CVE-2025-8671
CVE-2025-8671
A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS). By opening streams and then rapidly triggering the server to reset them—using malformed frames or flow control errors—an attacker can exploit incorrect stream accounting. Streams reset by the server are considered closed at the protocol level, even though backend processing continues. This allows a client to cause the server to handle an unbounded number of concurrent streams on a single connection. This CVE will be updated as affected product details are released.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
4%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (4)
Products (17)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-404
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1498.001Network Denial of Service: Direct Network Flood
- T1499Endpoint Denial of Service
- T1499.003Endpoint Denial of Service: Application Exhaustion Flood
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Indexed by
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /2.
References
17 on the record
- galbarnahum.com/made-you-reset
reference
- kb.cert.org/vuls/id/767506
reference
- varnish-cache.org/security/VSV00017.html
reference
- www.fastlystatus.com/incident/377810
reference
- github.com/h2o/h2o/commit/4729b661e3c6654198d2cc62997e1af58bef4b80
reference
- support2.windriver.com/index.php?page=security-notices
reference
- www.suse.com/support/kb/doc/?id=000021980
reference
- gitlab.isc.org/isc-projects/bind9/-/issues/5325
reference
Elsewhere on this site
- suse linuxevery CVE for this vendor
- varnish softwareevery CVE for this vendor
- fastlyevery CVE for this vendor
- CWE-404other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.