How severe is GHSA-wjpw-4j6x-6rwh?

GHSA-wjpw-4j6x-6rwh has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wjpw-4j6x-6rwh?

GHSA-wjpw-4j6x-6rwh affects the following packages: org.eclipse.jetty:jetty-http (Maven), org.eclipse.jetty:jetty-http (Maven), org.eclipse.jetty:jetty-http (Maven), org.eclipse.jetty:jetty-http (Maven), org.eclipse.jetty:jetty-http (Maven). Ecosystems affected: Maven.

How do I fix GHSA-wjpw-4j6x-6rwh?

A fix is available for GHSA-wjpw-4j6x-6rwh; check the affected-versions list above or the advisory for the patched release of org.eclipse.jetty:jetty-http, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-wjpw-4j6x-6rwh in my Maven dependencies?

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

How do I mitigate GHSA-wjpw-4j6x-6rwh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-wjpw-4j6x-6rwh actively exploited in the wild?

No public exploit code has been indexed for GHSA-wjpw-4j6x-6rwh 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-wjpw-4j6x-6rwh?

GHSA-wjpw-4j6x-6rwh has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-wjpw-4j6x-6rwh?

GHSA-wjpw-4j6x-6rwh is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wjpw-4j6x-6rwh published, and has it been updated?

GHSA-wjpw-4j6x-6rwh was published on March 5, 2026 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

org.eclipse.jetty:jetty-http has different parsing of invalid URIsGHSA-wjpw-4j6x-6rwh

LOW

GHSA-wjpw-4j6x-6rwh is a low-severity (CVSS 3.7) Improper Input Validation vulnerability in org.eclipse.jetty:jetty-http. A fix is available for org.eclipse.jetty:jetty-http — see the affected versions and patch details below.

Also known asCVE-2025-11143

Published

Mar 5, 2026

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

2 / 5

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wjpw-4j6x-6rwh.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs8th percentile — riskier than 8% 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

5 pkgs affected

☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http☕org.eclipse.jetty:jetty-http

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

The Jetty URI parser has some key differences compared to other common parsers when evaluating invalid or unusual URIs. Specifically:

Invalid Scheme

URI	Jetty	uri-js (nodejs)	node-url(nodejs)
`https>://vulndetector.com/path`	scheme=`http>`	scheme=`https`	invalid URI

Improper IPv4 mapped IPv6

URI	Jetty	System.Uri(CSharp)	curl(C)
`http://[0:0:0:0:0:ffff:127.0.0.1]`	invalid	host=`[::ffff:127.0.0.1]`	host=`[::ffff:127.0.0.1]`
`http://[::ffff:255.255.0.0]`	invalid	host=`[::ffff:255.255.0.0]`	host=`[::ffff:255.255.0.0]`

Incorrect IPv6 delimeter priority

URI	Jetty	urllib3(python)	furl(python)	Spring	chromium
`http://[normal.com@]vulndetector.com/`	host=`[normal.com@]`	invalid	invalid
`http://normal.com[user@vulndetector].com/`	host=`[noirmal.com@vulndetector			host=`normal.com`	invalid
`http://normal.com[@]vulndetector.com/`	host=`normal.com[@]			host=`normal.com`	invalid

Incorrect delimeter priority

URI	Jetty	urllib3(python)	jersey
`http://normal.com/#@vulndetector.com`	host=`vulndetector.com`	host=`normal.com`	host=`normal.com`
`http://normal.com/[email protected]`	host=`vulndetector.com`	host=`normal.com`	host=`normal.com`

Impact

Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.

Patches

Patched in Supported Open Source versions.

12.1.5 - Supported and available on Maven Central
12.0.31 - Supported and available on Maven Central
11.0.x - EOL Release, patches available on tuxcare and herodevs
10.0.x - EOL Release, patches available on tuxcare and herodevs
9.4.x - EOL Release, patches available on tuxcare and herodevs

Workarounds

None

Resources

Affected Packages

5 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-http`	≥ 9.4.0	No fix
☕Maven	`org.eclipse.jetty:jetty-http`	≥ 10.0.0	No fix
☕Maven	`org.eclipse.jetty:jetty-http`	≥ 11.0.0	No fix
☕Maven	`org.eclipse.jetty:jetty-http`	≥ 12.0.0&&< 12.0.31	12.0.31`org.eclipse.jetty:jetty-http:12.0.31`
☕Maven	`org.eclipse.jetty:jetty-http`	≥ 12.1.0&&< 12.1.5	12.1.5`org.eclipse.jetty:jetty-http:12.1.5`

Affected Products

1 product · 5 configurations

Application

jettyeclipse

≥ 12.1.0 && ≤ 11.0.26

range

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-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-wjpw-4j6x-6rwh; check the affected-versions list above or the advisory for the patched release of org.eclipse.jetty:jetty-http, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatLow

This vulnerability is rated as Low by Red Hat. Successful usage of this vulnerability is non-trivial, as the attacker must be able to craft a URI that exploits Jetty's differential parsing while bypassing other parsers (ex. in a firewall or load balancer). Additionally, divulging implementation details is possible but…

Product	Fixed in	Advisory
Red Hat Offline Knowledge Portal 1.2.13	`offline-knowledge-portal/rhokp-rhel9:1779996999`	RHSA-2026:21773

Frequently Asked Questions

The Jetty URI parser has some key differences compared to other common parsers when evaluating invalid or unusual URIs. Specifically: #### Invalid Scheme | URI | Jetty | uri-js (nodejs) | node-url(nodejs) | |---|---|---| --- | | `https>://vulndetector.com/path` | scheme=`http>`| scheme=`https` | invalid URI | #### Improper IPv4 mapped IPv6 | URI | Jetty | System.Uri(CSharp) | curl(C) | |---|---|---| --- | | `http://[0:0:0:0:0:ffff:127.0.0.1]` | invalid | host=`[::ffff:127.0.0.1]` | host=`[::ffff:127.0.0.1]` | | `http://[::ffff:255.255.0.0]` | invalid | host=`[::ffff:255.255.0.0]` | host=`[

O3 Security · Impact-Aware SCA

Is GHSA-wjpw-4j6x-6rwh in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 5, 2026

Last updated

Sep 10, 2026

Identifiers

GHSA-wjpw-4j6x-6rwh

References

Advisorynvd.nist.gov · CVE 2025 11143 Webgithub.com · GHSA wjpw 4j6x 6rwh Webgithub.com · Java.Eclipse.Jetty.Report .Incorrect.Parsing.Priority.of.the.IPv6.Hostname.Delimeter.pdf Webgithub.com · Java.Eclipse.Jetty.Report .The.Parsing.Priority.of.the.Delimiter.pdf Webgithub.com · Java.Eclipse.Jetty.Report .Parsing.Difference.Due.to.Deformed.Scheme.pdf Webgithub.com · Java.Eclipse.Jetty.Report .Improper.IPv4 mapped.IPv6.Parsing.pdf Packagegithub.com · jetty.project

Related vulnerabilities

Also affects jetty-http

This CVE is low severity; 5 of 5 other CVEs affecting jetty-http are rated as high or higher (top: high).

CVE-2026-2332CVE-2025-11143CVE-2024-6763CVE-2023-40167CVE-2022-2047

Same weakness: CWE-20

This CVE is low severity; 3 of 3 other CVEs with CWE-20 are rated as high or higher (top: moderate).

CVE-2026-118776CVE-2026-115779CVE-2026-125332Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026