# CVE-2025-9086: Out of bounds read for cookie path > An out-of-bounds read in curl's cookie path comparison can cause crashes or allow insecure sites to override secure cookies. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Sep 2025 - **Updated:** 15 Sep 2026 - **Also known as:** ALPINE-CVE-2025-9086, ALSA-2025:23383, ALSA-2026:1350, ALSA-2026:1825, BELL-CVE-2025-9086, CLEANSTART-2026-VE90255, CLSA-2026-1767807099, CLSA-2026-1767808644, CLSA-2026-1769092364, CLSA-2026-1770370767, CURL-CVE-2025-9086, DEBIAN-CVE-2025-9086, DLA-4432-1, ECHO-6a25-e091-8eb3, GHSA-v676-f8gm-92r9, JLSEC-2026-435, MGASA-2025-0232, MINI-vr3g-7rxg-wq23, OESA-2025-2319, RHSA-2025:23043, RHSA-2025:23125, RHSA-2025:23126, RHSA-2025:23127, RHSA-2025:23383, RHSA-2026:1350, RHSA-2026:1477, RHSA-2026:1825, RLSA-2025:23383, RLSA-2026:1350, RLSA-2026:1825, ROOT-OS-ALPINE-315-CVE-2025-9086, UBUNTU-CVE-2025-9086 ## What is CVE-2025-9086? CVE-2025-9086 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2025-9086? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `curl` | AlmaLinux:10 | All versions | 8.12.1-2.el10_1.2 | | `libcurl` | AlmaLinux:10 | All versions | 8.12.1-2.el10_1.2 | | `libcurl-devel` | AlmaLinux:10 | All versions | 8.12.1-2.el10_1.2 | | `libcurl-minimal` | AlmaLinux:10 | All versions | 8.12.1-2.el10_1.2 | | `curl` | AlmaLinux:8 | All versions | 7.61.1-34.el8_10.9 | | `libcurl` | AlmaLinux:8 | All versions | 7.61.1-34.el8_10.9 | | `libcurl-devel` | AlmaLinux:8 | All versions | 7.61.1-34.el8_10.9 | | `libcurl-minimal` | AlmaLinux:8 | All versions | 7.61.1-34.el8_10.9 | | `curl` | AlmaLinux:9 | All versions | 7.76.1-35.el9_7.3 | | `curl-minimal` | AlmaLinux:9 | All versions | 7.76.1-35.el9_7.3 | | `libcurl` | AlmaLinux:9 | All versions | 7.76.1-35.el9_7.3 | | `libcurl-devel` | AlmaLinux:9 | All versions | 7.76.1-35.el9_7.3 | | `libcurl-minimal` | AlmaLinux:9 | All versions | 7.76.1-35.el9_7.3 | | `curl` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `curl-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `curl-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `libcurl` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `libcurl-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `libcurl-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `libcurl-minimal` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `libcurl-minimal-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:8.12.1-2.el10_1.2 | | `curl` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `curl-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `curl-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `curl-minimal-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `libcurl` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `libcurl-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `libcurl-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `libcurl-minimal` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `libcurl-minimal-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:7.61.1-34.el8_10.9 | | `curl-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `curl-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `curl-minimal-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `libcurl-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `libcurl-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `libcurl-minimal-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.76.1-35.el9_7.3 | | `curl` | Red Hat:enterprise_linux:9::baseos | All versions | 0:7.76.1-35.el9_7.3 | | `curl-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:7.76.1-35.el9_7.3 | | `curl-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:7.76.1-35.el9_7.3 | | `curl-minimal` | Red Hat:enterprise_linux:9::baseos | All versions | 0:7.76.1-35.el9_7.3 | Products: Debian Debian Linux, Haxx Curl. ## How do I fix CVE-2025-9086? Upgrade to a fixed version. ## Is CVE-2025-9086 being exploited? There is no known exploitation of CVE-2025-9086 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-9086 and fix it if it is affected. What it is: CVE-2025-9086 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-9086 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-9086/ (Markdown: https://insights.sbomify.com/CVE-2025-9086/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9086 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9086 - OSV: https://osv.dev/vulnerability/CVE-2025-9086 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-9086/ Summaries are generated and may contain mistakes; the official description above is the record.