Bug 2528717 (CVE-2026-85152) - CVE-2026-85152 undici: undici: Authentication bypass via cross-origin cache poisoning due to missing origin isolation
Summary: CVE-2026-85152 undici: undici: Authentication bypass via cross-origin cache p...
Keywords:
Status: NEW
Alias: CVE-2026-85152
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-04 16:43 UTC by OSIDB Bzimport
Modified: 2026-09-30 20:53 UTC (History)
60 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:73428 0 None None None 2026-09-29 16:31:48 UTC
Red Hat Product Errata RHSA-2026:73838 0 None None None 2026-09-30 10:57:55 UTC
Red Hat Product Errata RHSA-2026:74085 0 None None None 2026-09-30 20:53:52 UTC

Description OSIDB Bzimport 2026-09-04 16:43:13 UTC
undici 8.10.0 omits the destination origin from the cache and request-deduplication keys when the cache or deduplicate interceptor is composed directly onto a Client or Pool. Because the internal cache key falls back to an empty origin string, a cacheable or in-flight response from one upstream origin is returned for a request to a different, trusted origin whenever the method, path, and relevant headers match, which permits cross-origin information disclosure and persistent cache poisoning. The reporter demonstrated a full authentication bypass in which a JWT signed with an attacker-controlled key was accepted as belonging to a trusted issuer, and the trusted origin was never contacted. This is a regression introduced in 8.10.0 and affects undici versions from 8.10.0 up to 8.10.2. Applications using an Agent, which carries the origin in its dispatch options, are not affected. Users should upgrade to undici 8.10.2.

Comment 1 Jon Orris 2026-09-29 16:31:45 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:73428 https://access.redhat.com/errata/RHSA-2026:73428

Comment 2 Jon Orris 2026-09-30 10:57:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:73838 https://access.redhat.com/errata/RHSA-2026:73838

Comment 3 Jon Orris 2026-09-30 20:53:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:74085 https://access.redhat.com/errata/RHSA-2026:74085


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