undici vulnerable to cross-origin cache poisoning via missing origin isolation in interceptors
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: undici undici 8.10.2.
Low priority for now. Upgrade to undici undici 8.10.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-346
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · openjs
- 7.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | undici | cpe:2.3:a:nodejs:undici |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs undici8.10.0 and later · before 8.10.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.
undici undici
- 8.10.2not affected
- 8.10.0 and later · before 8.10.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | nodejs24 | before 1:24.21.0-1.el10_2 | 1:24.21.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-devel | before 1:24.21.0-1.el10_2 | 1:24.21.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-docs | before 1:24.21.0-1.el10_2 | 1:24.21.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-full-i18n | before 1:24.21.0-1.el10_2 | 1:24.21.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-libs | before 1:24.21.0-1.el10_2 | 1:24.21.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-npm | before 2:11.19.0-1.24.21.0.1.el10_2 | 2:11.19.0-1.24.21.0.1.el10_2 |
| AlmaLinux:8 | nodejs | before 1:24.21.0-1.module_el8.10.0+4292+21afb960 | 1:24.21.0-1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | nodejs-devel | before 1:24.21.0-1.module_el8.10.0+4292+21afb960 | 1:24.21.0-1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | nodejs-docs | before 1:24.21.0-1.module_el8.10.0+4292+21afb960 | 1:24.21.0-1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.21.0-1.module_el8.10.0+4292+21afb960 | 1:24.21.0-1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | nodejs-libs | before 1:24.21.0-1.module_el8.10.0+4292+21afb960 | 1:24.21.0-1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | nodejs-nodemon | before 3.1.14-2.module_el8.10.0+4250+09238ed4 | 3.1.14-2.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | npm | before 1:11.19.0-1.24.21.0.1.module_el8.10.0+4292+21afb960 | 1:11.19.0-1.24.21.0.1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:8 | v8-13.6-devel | before 3:13.6.233.17-1.24.21.0.1.module_el8.10.0+4292+21afb960 | 3:13.6.233.17-1.24.21.0.1.module_el8.10.0+4292+21afb960 |
| AlmaLinux:9 | nodejs | before 1:24.21.0-1.module_el9.8.0+321+1555b6a2 | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 |
| AlmaLinux:9 | nodejs-devel | before 1:24.21.0-1.module_el9.8.0+321+1555b6a2 | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 |
| AlmaLinux:9 | nodejs-docs | before 1:24.21.0-1.module_el9.8.0+321+1555b6a2 | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:24.21.0-1.module_el9.8.0+321+1555b6a2 | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 |
| AlmaLinux:9 | nodejs-libs | before 1:24.21.0-1.module_el9.8.0+321+1555b6a2 | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 |
| AlmaLinux:9 | nodejs-nodemon | before 3.1.14-3.module_el9.8.0+292+f4eaf8b2 | 3.1.14-3.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-packaging | before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
| AlmaLinux:9 | nodejs-packaging-bundler | before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
+70
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-35949`undici.request` vulnerable to SSRF using absolute URL on `pathname`40Plan
- CVE-2026-1525undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')39Monitor
- CVE-2026-109829undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-85014Sep 4, 2026 · undici vulnerable to Denial of Service via WebSocketStream unclean close30Monitor
- ← EarlierCVE-2026-85024Sep 4, 2026 · undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression23Monitor
- Later →CVE-2026-18149Sep 4, 2026 · undici vulnerable to Denial of Service via orphaned RetryHandler response body23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| undici undici | 8.10.2 | Vendor (CNA) |
| almalinux:nodejs | 1:24.21.0-1.module_el8.10.0+4292+21afb960 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.21.0-1.module_el8.10.0+4292+21afb960 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:24.21.0-1.module_el8.10.0+4292+21afb960 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.21.0-1.module_el8.10.0+4292+21afb960 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.21.0-1.module_el8.10.0+4292+21afb960 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.21.0-1.module_el9.8.0+321+1555b6a2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.1.14-2.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.1.14-3.module_el9.8.0+292+f4eaf8b2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs24 | 1:24.21.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-devel | 1:24.21.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-docs | 1:24.21.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-full-i18n | 1:24.21.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-libs | 1:24.21.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-npm | 2:11.19.0-1.24.21.0.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:node-undici | 8.10.2+dfsg+~cs3.2.2-1 · Debian:14 | Package registry (OSV) |
| npm:undici | 8.10.2 | Package registry (OSV) |
| opensuse:pi-coding-agent | 1.0.4-bp160.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:grafana12.4 | 0:12.4.9-0.6.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24 | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-bin | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-debuginfo | 1:24.21.0-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:nodejs24-devel | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-docs | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-full-i18n | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-libs | 0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+14
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- nikolakojic-rasitreporter
- mcollinaremediation developer
- UlisesGasconremediation reviewer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-10982941 days apartundici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects36Monitor
- CVE-2026-673479 days apartundici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-346 · Origin Validation ErrorCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Exploit Script-Based APIsCAPEC-160Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-Middle: ARP Cache PoisoningT1557.002
- Compromise Infrastructure: DNS ServerT1584.002
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.