CVE-2025-5115

MadeYouReset HTTP/2 vulnerability

HIGH
7.5
CVSS Score
Published: August 20, 2025 at 07:07 PM UTC
Updated: June 17, 2026 at 09:47 AM UTC
2 products affected across 2 vendorsJettyJetty

Using Eclipse Jetty by Eclipse Jetty?

Get instant alerts when new vulnerabilities affect Eclipse Jetty - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 4%
SSVC
No known exploit

Description

In Eclipse Jetty, versions <=9.4.57, <=10.0.25, <=11.0.25, <=12.0.21, <=12.1.0.alpha2, an HTTP/2 client may trigger the server to send RST_STREAM frames, for example by sending frames that are malformed or that should not be sent in a particular stream state, therefore forcing the server to consume resources such as CPU and memory. For example, a client can open a stream and then send WINDOW_UPDATE frames with window size increment of 0, which is illegal. Per specification https://www.rfc-editor.org/rfc/rfc9113.html#name-window_update , the server should send a RST_STREAM frame. The client can now open another stream and send another bad WINDOW_UPDATE, therefore causing the server to consume more resources than necessary, as this case does not exceed the max number of concurrent streams, yet the client is able to create an enormous amount of streams in a short period of time. The attack can be performed with other conditions (for example, a DATA frame for a closed stream) that cause the server to send a RST_STREAM frame. Links: * https://github.com/jetty/jetty.project/security/advisories/GHSA-mmxm-8w33-wc4h

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0.0 ≤ v ≤ 10.0.2511.0.0 ≤ v ≤ 11.0.2512.0.0 ≤ v ≤ 12.0.219.3.0 ≤ v ≤ 9.4.57>=10.0.0 ≤ v ≤ <=10.0.25>=11.0.0 ≤ v ≤ <=11.0.25>=12.0.0 ≤ v ≤ <=12.0.21>=12.1.0.alpha0 ≤ v ≤ <=12.1.0.alpha2>=9.3.0 ≤ v ≤ <=9.4.5712.1.0 alpha012.1.0 alpha112.1.0 alpha2>=10.0.0>=11.0.0>=12.0.0>=12.1.0.alpha0>=9.3.0
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card