Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-hmr7-m48g-48f6

Jetty accepts "+" prefixed value in Content-Length

CVSS 5.3 MediumEPSS 0.013 · 70th percentile

Published by the GitHub Advisory Database at 14 Sept 2023, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.eclipse.jetty:jetty-httpMaven>=9.0.0, <9.4.52 || >=10.0.0, <10.0.16 || >=11.0.0, <11.0.16 || >=12.0.0, <12.0.19.4.52, 10.0.16, 11.0.16, 12.0.1
Identifiers
GHSA-hmr7-m48g-48f6 · CVE-2023-40167
Weakness (CWE)
CWE-130
Tags
Published
14 Sept 2023
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, versions 9.0.0 up to 9.4.52, 10.0.0 up to 10.0.16, 11.0.0 up to 11.0.16, and 12.0.0 up to 12.0.1, accepts a '+' character before the Content-Length value, which is more permissive than the RFC allows. The source gives few details on exploitation and states there is no known exploit scenario, though it notes request smuggling could be possible when Jetty sits in front of a server that does not close the connection after a 400 response. Upgrade to 9.4.52, 10.0.16, 11.0.16, or 12.0.1; no workaround is listed.

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
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.013, the 70th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 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.