CVE-2026-80255Published Sep 6, 2026 · Sep 6Updated Nov 3
secure cookie attribute bypass with tab
curl
High7.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
8.21.08.20.08.19.08.18.08.17.08.16.0| No fix yet |
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.
From the CVE record · curl
curl may store a cookie without its Secure flag when a Set-Cookie header has a tab immediately before the Secure attribute. If a subsequent request to the same host uses plaintext HTTP, the cookie might be sent over that connection. The input does not specify authentication or user-interaction requirements.
Engineers running curl should check their installations; affected versions were not provided.