cve.bz

CVE-2025-8671 Improper Resource Shutdown or Release

7.5 highEPSS 3.4%Fix available

High (7.5). EPSS 3.4% estimated probability of exploitation activity in the next 30 days. Fixed in pingora-core 0.6.0.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
3.4% (unchanged from 3.4% a week ago; 3.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2025-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-8671 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-8671?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-8671?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-8671 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
SUSE Linux Enterprise Module for Development Toolsfrom 15 SP2 before 15-SP5
SUSE Linux Enterprise High Performance Computing (HPC)from 15 before 15 SP5
Varnish Software Varnish Enterprisefrom 6.0.x through 6.0.14r4
Varnish Software Varnish Cachefrom 6.0LTS through 6.014
Varnish Software Varnish Cachefrom 5.x through 7.71
Fastly H20579ecfa
Wind River Linuxfrom LTS22 through TLS25
SUSE Linux Enterprise Desktopfrom 15 SP6 before 15 SP7
SUSE Linux Enterprise High Performance Computingfrom 15 SP3 before 15 SP7
SUSE Linux Enterprise Module for Dev Toolsfrom 15 SP3 before 15 SP7
SUSE Linux Enterprise Module for Package Hubfrom 15 SP5 before 15 SP7
SUSE Linux Enterprise Serverfrom 12 SP5 before 15 SP7
SUSE Linux Enterprise Server for SAP Applicationsfrom 15 SP6 before 15 SP7
SUSE Linux SUSE Manager Server4.3
SUSE Linux SUSE Manager Server LTS4.3
SUSE Linux SUSE Manager Proxy4.3
SUSE Linux SUSE Manager Retail Branch Server4.3
SUSE Linux openSUSE Leap15.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
RUSTSEC-2025-0070crates.iopingora-core>=0.0.0-0 <0.6.00.6.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12h2o, varnishno fix listedDEBIAN-CVE-2025-8671
Debian13varnish7.7.0-3+deb13u1DEBIAN-CVE-2025-8671 DSA-6303-1
Ubuntu14.04:LTSvarnishno fix listedUBUNTU-CVE-2025-8671
Ubuntu24.04:LTS, Pro:18.04:LTS, Pro:20.04:LTS and 1 moreh2o, varnish, lighttpdno fix listedUBUNTU-CVE-2025-8671
Ubuntu25.10dnsdist1.9.10-1ubuntu0.1UBUNTU-CVE-2025-8671 USN-8037-1
Ubuntu25.10, Pro:16.04:LTSvarnish, lighttpdno fix listedUBUNTU-CVE-2025-8671
Ubuntu26.04:LTS, 26.10, Pro:14.04:LTSlighttpdno fix listedUBUNTU-CVE-2025-8671
UbuntuPro:22.04:LTSdnsdist1.6.1-1ubuntu0.1~esm2USN-8037-1
UbuntuPro:24.04:LTSdnsdist1.8.3-2ubuntu0.1~esm1UBUNTU-CVE-2025-8671 USN-8037-1
SUSELinux Enterprise Module for Basesystem 15 SP7dnsdist1.9.11-150700.3.6.1SUSE-SU-2026:0888-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0dnsdist1.9.11-160000.1.1SUSE-SU-2026:20995-1
openSUSELeap 16.0dnsdist1.9.11-160000.1.1openSUSE-SU-2026:20461-1
openSUSELeap 16.0varnish7.7.3-bp160.1.1openSUSE-SU-2026:22131-1
openSUSETumbleweedbun1.4.4-1.1openSUSE-SU-2026:12316-1
openSUSETumbleweeddnsdist2.0.2-1.1openSUSE-SU-2026:10219-1
openSUSETumbleweedlighttpd1.4.80-1.1openSUSE-SU-2025:15448-1
Alpinev3.15, v3.16, v3.17 and 7 morelighttpd0-r0ALPINE-CVE-2025-8671
Alpinev3.22, v3.23, v3.24varnish7.7.2-r0ALPINE-CVE-2025-8671
Alpinev3.23, v3.24dnsdist2.0.1-r0ALPINE-CVE-2025-8671

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat's statement

This vulnerability is used to track additional modules, which may be vulnerable to the "MadeYouReset" attack. As Red Hat Product Security has not identified additional exposure, please reference these other vulnerabilities for detailed information: CVE-2025-48989, CVE-2025-55163, CVE-2025-5115, & CVE-2025-54500.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-8671.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON