Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

git-url-parse crate vulnerable to Regular Expression Denial of Service

CVE-2023-33290GHSA-qfh9-8p57-mjjj

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io git-url-parse

    Affected
    <= 0.4.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2023-33290: 0.76% estimated exploitation activity in the next 30 days; percentile 55.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The git-url-parse crate through 0.4.4 for Rust allows Regular Expression Denial of Service (ReDos) via a crafted URL to normalizeurl in lib.rs, a similar issue to CVE-2023-32758 (Python).

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-qfh9-8p57-mjjj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-33290

Advisory: git-url-parse crate vulnerable to Regular Expression Denial of Service
IDs: CVE-2023-33290, GHSA-qfh9-8p57-mjjj
Record: https://patchnext.com/advisories/cve-2023-33290 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io git-url-parse: affected <= 0.4.4

## Suggested inspection (read-only)
- crates.io git-url-parse: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on git-url-parse.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qfh9-8p57-mjjj (GitHub-reviewed advisory GHSA-qfh9-8p57-mjjj lists affected ranges: crates.io git-url-parse >=0 <=0.4.4)

Commands are suggestions: review each one before running it.

Loading voting…