Bug 2526727 - CVE-2026-75899 python-jupytext: fast-uri: Server-Side Request Forgery via repeated hostname percent-decoding [fedora-all]
Summary: CVE-2026-75899 python-jupytext: fast-uri: Server-Side Request Forgery via rep...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jupytext
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Jerry James
QA Contact:
URL:
Whiteboard: {"flaws": ["ba22faa8-b7a8-40bf-9476-3...
Depends On:
Blocks: CVE-2026-75899
TreeView+ depends on / blocked
 
Reported: 2026-09-01 10:16 UTC by Ganesh
Modified: 2026-09-01 10:16 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-09-01 10:16:41 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

fast-uri is a URI parser for Node.js. It decodes percent escapes in a hostname during parsing and then decodes the parsed hostname a second time during authority recomposition, so a single call to normalize or resolve can turn nested percent-encoded input into a different network destination such as a loopback hostname or address. For example, a doubly encoded host that spells out a loopback name decodes to that live host in one operation, which contradicts RFC 3986 section 2.4 that an implementation must not decode the same string more than once. An application that normalizes or resolves an untrusted HTTP-family URI before outbound routing, redirect validation, or a host-policy check can receive a destination different from the one the original encoded host represented, giving a server-side request forgery and host-policy bypass primitive. This is an incomplete-fix variant of CVE-2026-6322. The affected versions are 2.4.1 up to but not including 2.4.5, 3.1.2 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which normalize percent escapes once and preserve encoded percent signs. Users should upgrade to a patched version.


Note You need to log in before you can comment on or make changes to this bug.