published 6 Sep 2026 · updated 16 Nov 2026
secure cookie attribute bypass with tab
7.5HighCVSS 7.5EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4f6aa41a0145e930e766775dbe860883d350aa0a, 8.14.2, 8.16.1 and 2 more.
A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| curl | =8.13.0, =8.14.0, =8.14.1, =8.15.0, =8.16.0, =8.17.0, =8.18.0, =8.19.0, =8.20.0, =8.21.0, >=1aea05a6c2699e80c75936d58569851555acd603 <4f6aa41a0145e930e766775dbe860883d350aa0a, >=8.13.0 <8.14.2, >=8.15.0 <8.16.1, >=8.17.0 <8.20.1, >=8.21.0 <8.22.0 | 4f6aa41a0145e930e766775dbe860883d350aa0a, 8.14.2, 8.16.1, 8.20.1, 8.22.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket