Bug 2537768 - CVE-2026-75931 python-jupytext: fast-uri: Host confusion via skipped IDN canonicalization [fedora-all]
Summary: CVE-2026-75931 python-jupytext: fast-uri: Host confusion via skipped IDN cano...
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": ["5a04d3ab-4994-47dc-8289-5...
Depends On:
Blocks: CVE-2026-75931
TreeView+ depends on / blocked
 
Reported: 2026-09-22 08:53 UTC by Ganesh
Modified: 2026-09-22 08:53 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Ganesh 2026-09-22 08:53:25 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 canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree with each other: parse, resolve, normalize, and equal can yield different hosts for the same input depending only on whether a scheme is written out, and equal can return opposite verdicts for the same pair of hosts. An application that extracts a host with fast-uri to check it against a policy list and then resolves the same reference can make its decision on one host while the destination is another, enabling host confusion and policy bypass. The affected versions are 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which canonicalize the host consistently across the resolve path. Users should upgrade to a patched version.


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