Advisory record · GHSA-wjpw-4j6x-6rwh

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

CVSS 3.7 LowEPSS 0.0018 · 7th percentile

Published by the GitHub Advisory Database at 5 Mar 2026, 21:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.eclipse.jetty:jetty-httpMaven>=9.4.0, <=9.4.58 || >=10.0.0, <=10.0.26 || >=11.0.0, <=11.0.26 || >=12.0.0, <12.0.31 || >=12.1.0, <12.1.512.0.31, 12.1.5
Identifiers
GHSA-wjpw-4j6x-6rwh · CVE-2025-11143
Weakness (CWE)
CWE-20
Tags
Published
5 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jetty's jetty-http package (org.eclipse.jetty:jetty-http) versions 9.4.0 through 9.4.58, 10.0.0 through 10.0.26, 11.0.0 through 11.0.26, 12.0.0 before 12.0.31, and 12.1.0 before 12.1.5 parse some invalid or unusual URIs differently than other common parsers. An attacker can craft such a URI to bypass a component that filters URIs, such as a blocklist, or to reveal implementation details. Upgrade to 12.0.31 or 12.1.5; the source lists no workarounds, and the 9.4, 10.0 and 11.0 lines are end-of-life.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.7 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (eclipse)
  • CISA KEV Not listed.
  • EPSS 0.0018, the 7th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 5 Mar 2026, 10:09 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:17 UTC First seen by agentprime
  3. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.