org.eclipse.jetty:jetty-http vulnerabilities

Jetty HTTP Artifact

Registry
Maven
Latest
12.1.15

5 known advisories

The latest version, 12.1.15, is not affected by any of them. Projects on older versions may be.

Update to the latest version:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-http -DdepVersion=12.1.15 -DforceVersion=true

Is your project on an affected org.eclipse.jetty:jetty-http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for org.eclipse.jetty:jetty-http

  • HighCVE-2026-2332GHSA-355h-qmc2-wpwf14 Apr 2026

    Jetty has HTTP Request Smuggling via Chunked Extension Quoted-String Parsing

    Affected
    >=12.1.0 <12.1.7 · >=12.0.0 <12.0.33 · >=11.0.0 <11.0.29 · >=10.0.0 <10.0.28 · >=9.4.0 <9.4.60
    Fixed in
    9.4.60, 10.0.28, 11.0.29, 12.0.33, 12.1.7
  • LowCVE-2025-11143GHSA-wjpw-4j6x-6rwh5 Mar 2026

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

    Affected
    >=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
    Fixed in
    12.0.31, 12.1.5
  • MediumCVE-2024-6763GHSA-qh8g-58pp-2wxh14 Oct 2024

    Eclipse Jetty URI parsing of invalid authority

    Affected
    >=7.0.0 <12.0.12
    Fixed in
    12.0.12
  • MediumCVE-2023-40167GHSA-hmr7-m48g-48f614 Sept 2023

    Jetty accepts "+" prefixed value in Content-Length

    Affected
    >=9.0.0 <9.4.52 · >=10.0.0 <10.0.16 · >=11.0.0 <11.0.16 · >=12.0.0 <12.0.1
    Fixed in
    9.4.52, 10.0.16, 11.0.16, 12.0.1
  • LowCVE-2022-2047GHSA-cj7v-27pg-wf7q7 Jul 2022

    Jetty invalid URI parsing may produce invalid HttpURI.authority

    Affected
    <9.4.47 · >=10.0.0 <10.0.10 · >=11.0.0 <11.0.10
    Fixed in
    9.4.47, 10.0.10, 11.0.10

Is your org.eclipse.jetty:jetty-http version vulnerable?

Which of your client projects still run an old org.eclipse.jetty:jetty-http?

NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Maven packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.