CVE-2026-11525

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).

Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.

This was introduced in undici 5.15.0 when the cookies feature was added.

Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.

Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

Published

June 17, 2026

Last Modified

June 25, 2026

References (2)

Vendor Advisories for CVE-2026-11525(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatnodejs26-main-26.5.0-1.5.hum12026-07-25redhat
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs24-main-24.18.0-0.3.hum12026-07-11redhat
redhatnodejs26-main-26.5.0-1.3.hum12026-07-10redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 7.3.0+dfsg1+~cs24.12.11-2 (11 versions)
  • every version up to 8.5.0+dfsg+~cs3.2.0-1: fixed in 8.5.0+dfsg+~cs3.2.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • every version up to 6.27.0: fixed in 6.27.0
  • 7.0.0 up to 7.28.0: fixed in 7.28.0
  • 8.0.0 up to 8.5.0: fixed in 8.5.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 127 total refreshes for this CVE.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-02 16:40 UTCOSV refresh
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-09-30 15:02 UTCEPSS rescore
  6. 2026-09-29 15:20 UTCEPSS rescore
  7. 2026-09-28 13:50 UTCEPSS rescore
  8. 2026-09-26 15:58 UTCEPSS rescore
  9. 2026-09-23 13:47 UTCEPSS rescore
  10. 2026-09-20 20:15 UTCEPSS rescore
  11. 2026-09-18 19:27 UTCEPSS rescore
  12. 2026-09-16 05:14 UTCEPSS rescore
  13. 2026-09-13 16:46 UTCEPSS rescore
  14. 2026-09-13 14:12 UTCEG score recompute
  15. 2026-09-13 14:12 UTCVendor advisory
  16. 2026-09-12 15:00 UTCEPSS rescore
  17. 2026-09-11 14:52 UTCEPSS rescore
  18. 2026-09-11 09:36 UTCEPSS rescore
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 14:11 UTCEPSS rescore
  24. 2026-09-01 13:53 UTCEPSS rescore
  25. 2026-09-01 04:39 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 21:19 UTCEG score recompute
  2. 2026-08-30 21:19 UTCVendor advisory
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:21 UTCEPSS rescore
  5. 2026-08-28 21:40 UTCEPSS rescore
  6. 2026-08-27 14:24 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-23 04:14 UTCEG score recompute
  9. 2026-08-23 04:14 UTCVendor advisory
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:48 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-19 08:09 UTCEG score recompute
  15. 2026-08-19 08:09 UTCVendor advisory
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 15:45 UTCEG score recompute
  20. 2026-08-15 15:45 UTCVendor advisory
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-12 08:35 UTCEG score recompute
  25. 2026-08-12 08:35 UTCVendor advisory
  26. 2026-08-11 13:42 UTCEPSS rescore
  27. 2026-08-10 23:59 UTCEPSS rescore
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 01:26 UTCEG score recompute
  30. 2026-08-09 01:26 UTCVendor advisory
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-06 13:46 UTCEPSS rescore
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 18:17 UTCEG score recompute
  35. 2026-08-05 18:17 UTCVendor advisory
  36. 2026-08-04 15:09 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-03 10:35 UTCEPSS rescore
  39. 2026-08-02 10:43 UTCEG score recompute
  40. 2026-08-02 10:43 UTCVendor advisory
  41. 2026-08-02 02:26 UTCEPSS rescore
  42. 2026-08-01 04:15 UTCEPSS rescore
  43. 2026-07-30 16:27 UTCEPSS rescore
  44. 2026-07-30 03:34 UTCEG score recompute
  45. 2026-07-30 03:34 UTCVendor advisory
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-28 15:36 UTCEPSS rescore
  48. 2026-07-27 14:13 UTCEPSS rescore
  49. 2026-07-26 19:04 UTCEG score recompute
  50. 2026-07-26 19:04 UTCVendor advisory
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-25 14:17 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:04 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 14:30 UTCEPSS rescore
  61. 2026-07-19 02:28 UTCEPSS rescore
  62. 2026-07-18 10:04 UTCEPSS rescore
  63. 2026-07-16 17:02 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 02:00 UTCEPSS rescore
  66. 2026-07-14 10:24 UTCVendor advisory
  67. 2026-07-13 22:30 UTCEPSS rescore
  68. 2026-07-13 06:12 UTCEPSS rescore
  69. 2026-07-12 05:46 UTCEPSS rescore
  70. 2026-07-11 08:27 UTCEPSS rescore
  71. 2026-07-11 03:15 UTCVendor advisory
  72. 2026-07-09 19:10 UTCEPSS rescore
  73. 2026-07-08 15:15 UTCEPSS rescore
  74. 2026-07-08 15:15 UTCEPSS rescore
  75. 2026-07-07 20:00 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11525?
CVE-2026-11525 is a low vulnerability published on June 17, 2026. Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example,…
When was CVE-2026-11525 disclosed?
CVE-2026-11525 was first published on June 17, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11525 actively exploited?
CVE-2026-11525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11525?
CVE-2026-11525 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11525?
A fix for CVE-2026-11525 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11525 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11525

Explore →

Is Your Infrastructure Affected by CVE-2026-11525?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs