Answer in brief
CVE-2025-9086 records a Unknown severity vulnerability in Out of bounds read for cookie path. The current sources do not mark it as known exploited. The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| curl/curlgeneric | >=8.13.0 <8.14.2 || >=8.15.0 <8.16.0 | 8.14.2, 8.16.0 |
| curl/curlgeneric | >=1aea05a6c2699e80c75936d58569851555acd603 <c6ae07c6a541e0e96d0040afb62b45dd37711300 | c6ae07c6a541e0e96d0040afb62b45dd37711300 |
| curl/curlgeneric | 8.15.0 || 8.14.1 || 8.14.0 || 8.13.0 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.3 | V3.3 |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V4.0 | V4.0 |
| Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familygeneric | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCH328generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM324generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM328generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XCM332generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRH334 (24 V DC, 8xFO, CC)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230 V AC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (230 V AC, 8xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24 V DC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24V DC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (24 V DC, 8xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230 V AC, 12xFO)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230V AC, 2x10G, 24xSFP, 8xSFP+)generic | >=0 <V3.3 | V3.3 |
| Siemens/SCALANCE XRM334 (2x230 V AC, 8xFO)generic | >=0 <V3.3 | V3.3 |
Published upstream
Sep 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.