secure keyword for https://target
http://target (same
hostname, but using clear text HTTP) using the same cookie set path=\"/\",).
Since this site is not secure, the cookie should just be ignored.The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path.
The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
{
"cna_assigner": "curl",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/9xxx/CVE-2025-9086.json",
"unresolved_ranges": [
{
"source": "AFFECTED_FIELD",
"extracted_events": [
{
"last_affected": "8.15.0"
},
{
"last_affected": "8.14.1"
},
{
"last_affected": "8.14.0"
},
{
"last_affected": "8.13.0"
}
]
}
]
}