Answer in brief
CVE-2023-26049 records a Low severity (CVSS 2.4) vulnerability in Eclipse Jetty's cookie parsing of quoted values can exfiltrate values from other cookies. The current sources do not mark it as known exploited. The current feed maps org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.4. 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 org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven), org.eclipse.jetty:jetty-server (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.eclipse.jetty:jetty-servermaven | >=0 <9.4.51.v20230217 | 9.4.51.v20230217 |
| org.eclipse.jetty:jetty-servermaven | >=10.0.0 <10.0.14 | 10.0.14 |
| org.eclipse.jetty:jetty-servermaven | >=11.0.0 <11.0.14 | 11.0.14 |
| org.eclipse.jetty:jetty-servermaven | >=12.0.0alpha0 <12.0.0.beta0 | 12.0.0.beta0 |
Published upstream
Apr 18, 2023
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
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. ### Impact 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. ### Patches * 9.4.51.v20230217 - via PR #9352 * 10.0.15 - via PR #9339 * 11.0.15 - via PR #9339 ### Workarounds No workarounds ### References * https://www.rfc-editor.org/rfc/rfc2965 * https://www.rfc-editor.org/rfc/rfc6265
Quoted source text, attributed separately from HOL analysis.