CVE-2026-10725VulnerabilityPublished 20 Jun 2026Updated 17 Sep 2026

SUSE · Security update for perl-Protocol-HTTP2

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-10725· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade SUSE Protocol-HTTP2 to 1.13 soon.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.13

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Protocol::HTTP2 and Protocol-HTTP2 to 1.13.

Affected software

Product	Affected	Fixed in
CRUXProtocol::HTTP2	Affected <1.13	Fixed in 1.13
GitHubProtocol-HTTP2`pkg:github/Protocol-HTTP2`Other threats	Affected <1.13	Fixed in 1.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update has been released to fix this vulnerability. Users should apply the official update provided by the SUSE Product Security Team to remediate the issue. Patch status is not explicitly confirmed in the input data, so users should verify the availability of the update with the vendor advisory.

Description

A security update for perl-Protocol-HTTP2 addresses a denial of service vulnerability identified as CVE-2026-10725. The issue arises from the absence of an inbound HPACK header-list size limit, which could be exploited to cause denial of service. This vulnerability has been assigned a high severity level. There is no information about known exploits in the wild or a CVSS score. The update fixes this issue to prevent potential denial of service attacks.

Impact

The vulnerability can be exploited to cause denial of service by sending inbound HPACK header lists without size limits, potentially exhausting resources or causing service disruption in affected perl-Protocol-HTTP2 implementations.

Summary

CVE-2026-10725 is a denial of service vulnerability in perl-Protocol-HTTP2 caused by the lack of an inbound HPACK header-list size limit. This absence allows an attacker to potentially overwhelm the system by sending excessively large header lists, leading to denial of service conditions. The vulnerability has been addressed by a security update from the SUSE Product Security Team.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:17 UTC

Technical details

References

Community reviews

Related threats