Skip to content

Different parsing of invalid URIs

Low
olamy published GHSA-wjpw-4j6x-6rwh Mar 5, 2026

Package

maven org.eclipse.jetty:jetty-http (Maven)

Affected versions

>=9.4.0, <=9.4.58
>=10.0.0, <=10.0.26
>=11.0.0, <=11.0.26
>=12.0.0, <=12.0.30
>=12.1.0, <=12.1.4

Patched versions

12.0.31
12.1.5

Description

The Jetty URI parser has some key differences 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/?@vulndetector.com 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

References

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE ID

CVE-2025-11143

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

Credits