Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-11143

org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing

Overview

Published
5 Mar 2026
Modified
17 Jun 2026
Medium CVE
16 Registry packages
93 OS packages
8 Linux distributions
Yes Fix available

Description

The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. 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.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-20

Affected packages · 16

Packages affected by CVE-2025-11143
EcosystemPackageVulnerableFixed in
Maven org.eclipse.jetty:jetty-http >=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.5 12.0.3112.1.5
Seal Maven org.apache.hadoop:hadoop-client-runtime >=3.4.0+sp0, <3.4.0+sp999>=3.4.1+sp0, <3.4.1+sp999>=3.4.2+sp0, <3.4.2+sp999>=3.4.3+sp0, <3.4.3+sp2 3.4.0+sp9993.4.1+sp9993.4.2+sp9993.4.3+sp2
Seal Maven org.apache.spark:spark-core_2.11 >=2.4.8+sp0, <2.4.8+sp999 2.4.8+sp999
Seal Maven org.apache.spark:spark-core_2.13 >=4.0.1+sp0, <4.0.1+sp999 4.0.1+sp999
Seal Maven org.eclipse.jetty:jetty-http >=10.0.19+sp0, <10.0.19+sp999>=10.0.22+sp0, <10.0.22+sp999>=11.0.23+sp0, <11.0.23+sp999>=11.0.24+sp0, <11.0.24+sp2>=9.4.51.v20230217+sp0, <9.4.51.v20230217+sp2+2 more 10.0.19+sp99910.0.22+sp99911.0.23+sp99911.0.24+sp29.4.51.v20230217+sp2
Seal Maven seal.sp1.org.apache.hadoop:hadoop-client-runtime >=3.4.0, <3.4.0+sp999>=3.4.1, <3.4.1+sp999>=3.4.2, <3.4.2+sp999>=3.4.3, <3.4.3+sp999 3.4.0+sp9993.4.1+sp9993.4.2+sp9993.4.3+sp999
Seal Maven seal.sp1.org.apache.spark:spark-core_2.11 >=2.4.8, <2.4.8+sp999 2.4.8+sp999
Seal Maven seal.sp1.org.apache.spark:spark-core_2.13 >=4.0.1, <4.0.1+sp999 4.0.1+sp999
Seal Maven seal.sp1.org.eclipse.jetty:jetty-http >=10.0.19, <10.0.19+sp999>=10.0.22, <10.0.22+sp999>=11.0.23, <11.0.23+sp999>=11.0.24, <11.0.24+sp999>=9.4.51.v20230217, <9.4.51.v20230217+sp999+2 more 10.0.19+sp99910.0.22+sp99911.0.23+sp99911.0.24+sp9999.4.51.v20230217+sp999
Seal Maven seal.sp2.org.apache.hadoop:hadoop-client-runtime >=3.4.0, <3.4.0+sp999>=3.4.1, <3.4.1+sp999>=3.4.2, <3.4.2+sp999 3.4.0+sp9993.4.1+sp9993.4.2+sp999
Seal Maven seal.sp2.org.apache.spark:spark-core_2.11 >=2.4.8, <2.4.8+sp999 2.4.8+sp999
Seal Maven seal.sp2.org.eclipse.jetty:jetty-http >=9.4.53.v20231009, <9.4.53.v20231009+sp999>=9.4.56.v20240826, <9.4.56.v20240826+sp999 9.4.53.v20231009+sp9999.4.56.v20240826+sp999
Seal Maven seal.sp3.org.apache.hadoop:hadoop-client-runtime >=3.4.0, <3.4.0+sp999>=3.4.1, <3.4.1+sp999 3.4.0+sp9993.4.1+sp999
Seal Maven seal.sp4.org.apache.hadoop:hadoop-client-runtime >=3.4.0, <3.4.0+sp999>=3.4.1, <3.4.1+sp999 3.4.0+sp9993.4.1+sp999
Seal Maven seal.sp5.org.apache.hadoop:hadoop-client-runtime >=3.4.0, <3.4.0+sp999>=3.4.1, <3.4.1+sp999 3.4.0+sp9993.4.1+sp999
Seal Maven seal.sp6.org.apache.hadoop:hadoop-client-runtime >=3.4.1, <3.4.1+sp999 3.4.1+sp999

Open a package to see all its vulnerabilities.

Operating systems · 92 fixes

Red Hat 4 releases · 2 packages

affected 4 eol 3
jetty-http puppetserver
Red Hat fixes for CVE-2025-11143
ReleasePackageFixed in
7 jetty-http +1 affected
7 jetty-http eol
7 (satellite:el8) puppetserver affected
8 jetty-http affected
8 jetty-http eol
9 jetty-http +1 affected

1 more row

SUSE Linux Enterprise 1 release · 1 package

fixed 1
jetty-continuation
SUSE Linux Enterprise fixes for CVE-2025-11143
ReleasePackageFixed inAdvisory
15.7 jetty-continuation +7 9.4.58-150200.3.37.1 SUSE-SU-2026:1461-1

chainguard 1 release · 42 packages

fixed 42
cloudwatch-exporter akhq celeborn-0-5 spark-kubernetes-operator-fips spark-kubernetes-operator pinot +36
chainguard fixes for CVE-2025-11143
ReleasePackageFixed in
cloudwatch-exporter 0.18.0-r5
akhq 0.26.0-r10
celeborn-0-5 0.5.4-r26
spark-kubernetes-operator-fips 0.7.0-r1
spark-kubernetes-operator 0.9.0-r0
pinot +1 1.5.0-r0

36 more rows

debian 4 releases · 2 packages

affected 4 fixed 1
jetty9 jetty12
debian fixes for CVE-2025-11143
ReleasePackageFixed in
11 jetty9 affected
12 jetty9 affected
13 jetty12 +1 affected
14 jetty9 affected
14 jetty12 12.0.32-1

echo 1 release · 1 package

affected 1
jetty12
echo fixes for CVE-2025-11143
ReleasePackageFixed in
jetty12 +1 affected

minimos 1 release · 20 packages

fixed 20
cloudwatch-exporter strimzi-kafka-operator-0-45 strimzi-kafka-operator-fips-0-50 strimzi-kafka-operator jenkins neo4j-2026-02 +14
minimos fixes for CVE-2025-11143
ReleasePackageFixed in
cloudwatch-exporter 0.17.0-r0
strimzi-kafka-operator-0-45 0.45.2-r3
strimzi-kafka-operator-fips-0-50 0.50.1-r1
strimzi-kafka-operator 0.51.0-r1
jenkins 2.542-r0
neo4j-2026-02 2026.02.3-r0

14 more rows

openSUSE 1 release · 1 package

fixed 1
jetty-annotations
openSUSE fixes for CVE-2025-11143
ReleasePackageFixed inAdvisory
Tumbleweed jetty-annotations +29 9.4.58-3.1 openSUSE-SU-2026:10300-1

wolfi 1 release · 15 packages

fixed 15
cloudwatch-exporter akhq apache-tika-3-1 apache-tika-3-2 apache-tika-3-3 zookeeper-3-9 +9
wolfi fixes for CVE-2025-11143
ReleasePackageFixed in
cloudwatch-exporter 0.18.0-r5
akhq 0.26.0-r10
apache-tika-3-1 3.1.0-r38
apache-tika-3-2 3.2.3-r18
apache-tika-3-3 3.3.2-r2
zookeeper-3-9 3.9.5-r0

9 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.