How severe is GHSA-p26g-97m4-6q7c?

GHSA-p26g-97m4-6q7c has a CVSS score of 2.4/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-p26g-97m4-6q7c?

GHSA-p26g-97m4-6q7c affects the following packages: org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p26g-97m4-6q7c?

Update org.eclipse.jetty:jetty-server to 9.4.51.v20230217 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p26g-97m4-6q7c is resolved across your whole dependency graph.

How do I detect GHSA-p26g-97m4-6q7c in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p26g-97m4-6q7c if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-p26g-97m4-6q7c actively exploited in the wild?

No public exploit code has been indexed for GHSA-p26g-97m4-6q7c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p26g-97m4-6q7c?

GHSA-p26g-97m4-6q7c has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p26g-97m4-6q7c?

GHSA-p26g-97m4-6q7c is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p26g-97m4-6q7c published, and has it been updated?

GHSA-p26g-97m4-6q7c was published on April 18, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

Eclipse Jetty's cookie parsing of quoted values can exfiltrate values from other cookiesGHSA-p26g-97m4-6q7c

LOWFix: eclipse/jetty.project#9339

GHSA-p26g-97m4-6q7c is a low-severity (CVSS 2.4) Information Exposure vulnerability in org.eclipse.jetty:jetty-server. A fix is available for org.eclipse.jetty:jetty-server — see the affected versions and patch details below.

Also known asCVE-2023-26049

Published

Apr 18, 2023

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	all versions	9.4.51.v20230217`org.eclipse.jetty:jetty-server:9.4.51.v20230217`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 10.0.0&&< 10.0.14	10.0.14`org.eclipse.jetty:jetty-server:10.0.14`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 11.0.0&&< 11.0.14	11.0.14`org.eclipse.jetty:jetty-server:11.0.14`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 12.0.0alpha0&&< 12.0.0.beta0	12.0.0.beta0`org.eclipse.jetty:jetty-server:12.0.0.beta0`

Affected Products

6 products · 14 configurations

debian linuxdebian

3 versions

10.011.012.0

Application

jettyeclipse

≥ 11.0.0 && < 11.0.14

1 version

12.0.0

Application

active iq unified managernetapp

all

Application

e-series santricity os controllernetapp

≥ 11.0

range

Application

e-series santricity unified managernetapp

all

Application

e-series santricity web servicesnetapp

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-server to 9.4.51.v20230217 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p26g-97m4-6q7c is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.426.3.1706515686-3.el8`	RHSA-2024:0778
Red Hat AMQ Streams 2.5.0	see advisory	RHSA-2023:5165
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-undertow-0:2.2.28-1.SP1_redhat_00001.1.el8eap`	RHSA-2023:7638
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9	`eap7-undertow-0:2.2.28-1.SP1_redhat_00001.1.el9eap`	RHSA-2023:7639
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-undertow-0:2.2.28-1.SP1_redhat_00001.1.el7eap`	RHSA-2023:7637
Red Hat JBoss Enterprise Application Platform Expansion Pack	`jetty-server`	RHSA-2024:3385
Red Hat Satellite 6.14 for RHEL 8	`puppetserver-0:7.14.0-1.el8sat`	RHSA-2024:0797
Red Hat Single Sign-On 7	`jetty-server`	RHSA-2024:0804

Frequently Asked Questions

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