# CVE-2023-26049: Cookie parsing of quoted values can exfiltrate values from other cookies in Eclipse Jetty > Attackers can exfiltrate HttpOnly cookies and bypass intermediary policies by exploiting nonstandard quoted cookie parsing in Eclipse Jetty. - **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 18 Apr 2023 - **Updated:** 13 Feb 2025 - **Also known as:** CLEANSTART-2026-CA01896, CLEANSTART-2026-UA75354, CLSA-2026-1787550865, DEBIAN-CVE-2023-26049, GHSA-p26g-97m4-6q7c, UBUNTU-CVE-2023-26049 ## What is CVE-2023-26049? CVE-2023-26049 is a low-severity vulnerability in Debian Debian Linux, published on 18 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `"` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE="b; JSESSIONID=1337; c=d"` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-26049? 8 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.jetty:jetty-server` | Maven | All versions | 9.4.51.v20230217 | | `org.eclipse.jetty:jetty-server` | Maven | All versions | 9.4.51.v20230217 | | `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.14 | | `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.14 | | `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.14 | | `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.14 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0alpha0 | 12.0.0.beta0 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0alpha0 | 12.0.0.beta0 | Products: Debian Debian Linux, Eclipse Jetty, Netapp Active Iq Unified Manager, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Unified Manager, Netapp E-Series Santricity Web Services. ## How do I fix CVE-2023-26049? Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 9.4.51.v20230217, 10.0.14, 11.0.14 or 12.0.0.beta0. ## Is CVE-2023-26049 being exploited? There is no known exploitation of CVE-2023-26049 in the wild and no public exploit code. Public exploit code: - https://github.com/uthrasri/jetty-9.4.31.v20200723_CVE-2023-26049 (github_poc): https://github.com/uthrasri/jetty-9.4.31.v20200723_CVE-2023-26049 ## 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-2023-26049 and fix it if it is affected. What it is: CVE-2023-26049 is a low-severity vulnerability in Debian Debian Linux, published on 18 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-26049 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.jetty:jetty-server (Maven): affected all versions; fixed in 9.4.51.v20230217 - org.eclipse.jetty:jetty-server (Maven): affected all versions; fixed in 9.4.51.v20230217 - org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.14 - org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.14 - org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.14 - org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.14 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0alpha0; fixed in 12.0.0.beta0 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0alpha0; fixed in 12.0.0.beta0 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-2023-26049/ (Markdown: https://insights.sbomify.com/CVE-2023-26049/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26049 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26049 - OSV: https://osv.dev/vulnerability/CVE-2023-26049 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-26049/ Summaries are generated and may contain mistakes; the official description above is the record.