CVE-2026-11525
Last modified
CVE-2026-11525 is a low-severity vulnerability rated 3.7/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Undici | < 6.27.0 |
| Nodejs | Undici | >= 7.0.0, < 7.28.0 |
| Nodejs | Undici | >= 8.0.0, < 8.5.0 |
References
- https://cna.openjsf.org/security-advisories.htmlVendor Advisory
- https://github.com/nodejs/undici/security/advisories/GHSA-g8m3-5g58-fq7mMitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-11525?
How severe is CVE-2026-11525?
How do I fix CVE-2026-11525?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-115243The WPvivid — Backup, Migration & Staging WordPress plugin b…6.7
- CVE-2026-115245The Chat AI with Dispatcher WordPress plugin before 2.4 does…9.8
- CVE-2026-115246A weakness has been identified in subhajitkhan online-clinic…3.5
- CVE-2026-115247A security vulnerability has been detected in subhajitkhan o…4.3
- CVE-2026-115248A vulnerability was detected in subhajitkhan online-clinic-m…5.4
- CVE-2026-115249A flaw has been found in subhajitkhan online-clinic-manageme…4.6
- CVE-2026-115250The Text Typing WordPress plugin before 2.2.2 does not prop…6.8
- CVE-2026-115251The Duplicator WordPress plugin before 5.0.0 does not restr…7.2
- CVE-2026-115252The Confection WordPress Cable WordPress plugin from 0.4.0 t…10
- CVE-2026-115253An incorrect permission assignment vulnerability in the Watc…7.3
- CVE-2026-115255The WP Roster WordPress plugin before 2.35 does not perform …5.3
- CVE-2026-115256The Mail Debug for WooCommerce WordPress plugin through 1.3.…7.5
Are you affected by CVE-2026-11525?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
