Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

GHSA-wjpw-4j6x-6rwh — jetty-http

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.

org.eclipse.jetty:jetty-http has different parsing of invalid URIs

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 Sep 24, 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 Risk0.00%
Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-wjpw-4j6x-6rwh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

URIJettyuri-js (nodejs)node-url(nodejs)
https>://vulndetector.com/pathscheme=http>scheme=httpsinvalid URI

Improper IPv4 mapped IPv6

URIJettySystem.Uri(CSharp)curl(C)
http://[0:0:0:0:0:ffff:127.0.0.1]invalidhost=[::ffff:127.0.0.1]host=[::ffff:127.0.0.1]
http://[::ffff:255.255.0.0]invalidhost=[::ffff:255.255.0.0]host=[::ffff:255.255.0.0]

Incorrect IPv6 delimeter priority

URIJettyurllib3(python)furl(python)Springchromium
http://[normal.com@]vulndetector.com/host=[normal.com@]invalidinvalid
http://normal.com[user@vulndetector].com/host=`[noirmal.com@vulndetectorhost=normal.cominvalid
http://normal.com[@]vulndetector.com/host=`normal.com[@]host=normal.cominvalid

Incorrect delimeter priority

URIJettyurllib3(python)jersey
http://normal.com/#@vulndetector.comhost=vulndetector.comhost=normal.comhost=normal.com
http://normal.com/[email protected]host=vulndetector.comhost=normal.comhost=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
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.jetty:jetty-http≥ 9.4.0No fix
☕Mavenorg.eclipse.jetty:jetty-http≥ 10.0.0No fix
☕Mavenorg.eclipse.jetty:jetty-http≥ 11.0.0No fix
☕Mavenorg.eclipse.jetty:jetty-http≥ 12.0.0&&< 12.0.3112.0.31org.eclipse.jetty:jetty-http:12.0.31
☕Mavenorg.eclipse.jetty:jetty-http≥ 12.1.0&&< 12.1.512.1.5org.eclipse.jetty:jetty-http:12.1.5

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    No patched version of org.eclipse.jetty:jetty-http has shipped for GHSA-wjpw-4j6x-6rwh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wjpw-4j6x-6rwh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wjpw-4j6x-6rwh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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…

ProductFixed inAdvisory
Red Hat Offline Knowledge Portal 1.2.13offline-knowledge-portal/rhokp-rhel9:1779996999RHSA-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?

O3 Security finds GHSA-wjpw-4j6x-6rwh across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-wjpw-4j6x-6rwh: jetty-http (Low 3.7) | O3 Security