Skip to main content
VulnerabilityPublished Updated

CVE-2025-5115: Eclipse Jetty · Uncontrolled Resource Consumption

Affects Eclipse JettySource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High.

Data as of 4 Nov 2026, 17:33 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 4.07.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Eclipse Jetty Eclipse JettyAffected
  • >=9.3.0
  • >=10.0.0
  • >=11.0.0
  • >=12.0.0
  • >=12.1.0.alpha0
  • >=9.3.0 <=9.4.57
  • >=10.0.0 <=10.0.25
  • >=11.0.0 <=11.0.25
  • >=12.0.0 <=12.0.21
  • >=12.1.0.alpha0 <=12.1.0.alpha2
Fixed in–

AI-suggested

Until a fix is available, consider limiting or filtering HTTP/2 traffic from untrusted clients or deploying rate limiting to mitigate potential resource exhaustion attacks.

Description

CVE-2025-5115 is a high-severity vulnerability in Eclipse Jetty HTTP/2 server versions up to 9.4.57, 10.0.25, 11.0.25, 12.0.21, and 12.1.0.alpha2. It allows an HTTP/2 client to cause uncontrolled resource consumption by sending malformed or protocol-violating frames, such as WINDOW_UPDATE frames with zero window size increments. This forces the server to send RST_STREAM frames repeatedly, consuming CPU and memory resources. The issue arises because the server processes these invalid frames by opening many streams and responding with RST_STREAM frames, leading to excessive resource use without exceeding the maximum concurrent streams limit.

References

Community reviews

Loading reviews…