Microsoft advisory for CVE-2025-9086
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-9086. This page also shows what EchelonGraph holds for CVE-2025-9086, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products11
- azl3 cmake 3.30.3-10 on Azure Linux 3.0
- azl3 cmake 3.30.3-9 on Azure Linux 3.0
- azl3 curl 8.11.1-3 on Azure Linux 3.0
- azl3 curl 8.11.1-4 on Azure Linux 3.0
- cbl2 cmake 3.21.4-18 on CBL Mariner 2.0
- cbl2 cmake 3.21.4-19 on CBL Mariner 2.0
- cbl2 cmake 3.21.4-20 on CBL Mariner 2.0
- cbl2 curl 8.8.0-6 on CBL Mariner 2.0
- cbl2 curl 8.8.0-7 on CBL Mariner 2.0
- cbl2 mysql 8.0.43-1 on CBL Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL Mariner 2.0
🧭 EchelonGraph on CVE-2025-9086
- EchelonGraph score
- 7.5 HIGH
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
1. A cookie is set using the `secure` keyword for `https://target` 2. curl is redirected to or otherwise made to speak with `http://target` (same hostname, but using clear text HTTP) using the same cookie set 3. The same cookie name is set - but with only a slash as path (`path="/"`). Since this site is not secure, the cookie *should* be ignored. 4. A bug in the path comparison logic makes curl read outside a heap buffer boundary 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.
Published by curl, the CVE Numbering Authority that assigned CVE-2025-9086, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).