Bug 2579580 - CVE-2026-120415 openclaw: undici: Information disclosure via unstripped headers during cross-origin redirects [fedora-all]
Summary: CVE-2026-120415 openclaw: undici: Information disclosure via unstripped heade...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: openclaw
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tom.Rix
QA Contact:
URL:
Whiteboard: {"flaws": ["f7524fee-ec2d-4b22-9df5-6...
Depends On:
Blocks: CVE-2026-120415
TreeView+ depends on / blocked
 
Reported: 2026-11-20 18:04 UTC by Avinash Hanwate
Modified: 2026-11-20 18:04 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Avinash Hanwate 2026-11-20 18:04:13 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.

undici is an HTTP client for Node.js. In versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3, the redirect interceptor strips sensitive headers such as Authorization, Cookie, Proxy-Authorization, and Host when a request is redirected to a different origin, but when request headers are supplied as an array of name and value tuples (a valid documented input, for example from Object.entries), the redirect handler misreads them as a flat list so the header names never match and the sensitive headers are not removed. If a header-normalizing interceptor such as cache or deduplicate is composed outside the redirect interceptor, it then serializes the retained headers onto the cross-origin request, disclosing the caller's origin-bound credentials to the unrelated redirect destination. This is a representation-dependent bypass of the cross-origin header stripping added in CVE-2024-30260. The issue is fixed in undici 7.30.2 and 8.12.4, and users should upgrade to one of those versions or later. As a workaround, supply request headers as a plain object or a flat name and value array rather than an array of tuples, or compose the redirect interceptor outside the normalizing interceptor.


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