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
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.6% (FIRST EPSS); higher than 89.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: lighttpd (Alpine:v3.15) 0-r0; varnish (Alpine:v3.22) 7.7.2-r0; pingora-core (crates.io) 0.6.0.
Low priority for now. Upgrade to lighttpd (Alpine:v3.15) 0-r0; varnish (Alpine:v3.22) 7.7.2-r0; pingora-core (crates.io) 0.6.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Aug 13, 2025
- Updated
- Jun 17, 2026
- EPSS
- 3.6% · 89th percentile
- CWE
- CWE-404
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
Fastly H20
- 579ecfaaffected
SUSE Linux Enterprise Desktop
- 15 SP6 and later · before 15 SP7affected
SUSE Linux Enterprise High Performance Computing
- 15 SP3 and later · before 15 SP7affected
SUSE Linux Enterprise High Performance Computing (HPC)
- 15 and later · before 15 SP5affected
SUSE Linux Enterprise Module for Dev Tools
- 15 SP3 and later · before 15 SP7affected
SUSE Linux Enterprise Module for Development Tools
- 15 SP2 and later · before 15-SP5affected
SUSE Linux Enterprise Module for Package Hub
- 15 SP5 and later · before 15 SP7affected
SUSE Linux Enterprise Server
- 12 SP5 and later · before 15 SP7affected
SUSE Linux Enterprise Server for SAP Applications
- 15 SP6 and later · before 15 SP7affected
SUSE Linux openSUSE Leap
- 15.6affected
SUSE Linux SUSE Manager Proxy
- 4.3affected
SUSE Linux SUSE Manager Retail Branch Server
- 4.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.15 | lighttpd | before 0-r0 | 0-r0 |
| Alpine:v3.22 | varnish | before 7.7.2-r0 | 7.7.2-r0 |
| crates.io | pingora-core | from 0.0.0-0 · before 0.6.0 | 0.6.0 |
| Debian:12 | h2o | from 0 | — |
| Debian:12 | varnish | from 0 | — |
| Debian:13 | varnish | before 7.7.0-3+deb13u1 | 7.7.0-3+deb13u1 |
| openSUSE:Leap 16.0 | dnsdist | before 1.9.11-160000.1.1 | 1.9.11-160000.1.1 |
| openSUSE:Leap 16.0 | varnish | before 7.7.3-bp160.1.1 | 7.7.3-bp160.1.1 |
| openSUSE:Tumbleweed | dnsdist | before 2.0.2-1.1 | 2.0.2-1.1 |
| openSUSE:Tumbleweed | lighttpd | before 1.4.80-1.1 | 1.4.80-1.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | dnsdist | before 1.9.11-150700.3.6.1 | 1.9.11-150700.3.6.1 |
| SUSE:Linux Enterprise Server 16.0 | dnsdist | before 1.9.11-160000.1.1 | 1.9.11-160000.1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:lighttpd | 0-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:varnish | 7.7.2-r0 · Alpine:v3.22 | Package registry (OSV) |
| crates.io:pingora-core | 0.6.0 | Package registry (OSV) |
| debian:varnish | 7.7.0-3+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:dnsdist | 2.0.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:lighttpd | 1.4.80-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:varnish | 7.7.3-bp160.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:dnsdist | 1.9.11-150700.3.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×5
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:6 | 2025-08-18 |
| Proof-of-concept repository on GitHub | stars:2 | 2025-08-21 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-08-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-02-09 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-06-01 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+5 d
- TodayOct 26, 2026+439 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-404 · Improper Resource Shutdown or ReleaseCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (16 more)Show less
- github.com/h2o/h2o/commit/4729b661e3c6654198d2cc62997e1af58bef4b80
- github.com/h2o/h2o/security/advisories/GHSA-mrjm-qq9m-9mjq
- gitlab.isc.org/isc-projects/bind9/-/issues/5325
- kb.cert.org/vuls/id/767506
- support2.windriver.com/index.php?page=security-notices
- varnish-cache.org/security/VSV00017.html
- www.fastlystatus.com/incident/377810
- www.suse.com/support/kb/doc/?id=000021980
- www.openwall.com/lists/oss-security/2025/08/13/6
- www.openwall.com/lists/oss-security/2025/09/18/1
- deepness-lab.org/publications/madeyoureset/
- github.com/Kong/kong/discussions/14731
- github.com/envoyproxy/envoy/issues/40739
- github.com/varnish/hitch/issues/397
- www.imperva.com/blog/madeyoureset-turning-http-2-server-against-itself/
- www.kb.cert.org/vuls/id/767506
Vendor advisories and official records. Exploit/PoC links are deliberately left out.