VulnerabilityPublished 13 Aug 2026Updated 29 Oct 2026

CVE-2025-43859: Glances · h11 accepts some malformed Chunked-Encoding bodies

Affects glancesSource GCVE Database

Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.3.1_2 as a priority.

Data as of 30 Oct 2026, 09:00 UTC

CVSS 3.1 base score

9.1Critical

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

Patch: Available – fixed in 4.3.1_2

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

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 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 29 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 glances to 4.3.1_2.

Affected software

Product	Affected	Fixed in
Homebrewglances`pkg:brew/glances`Other threats	Affected >=4.2.1 <4.3.1_2	Fixed in 4.3.1_2

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

AI-suggested

A patch is available in h11 version 0.15.0, which corrects the chunked encoding parsing to strictly validate trailing '\r\n' bytes. Glances users should upgrade to version 4.3.1_2 or later, which includes the fixed h11 version. Since exploitation requires both a vulnerable h11 and a buggy proxy, fixing either component mitigates the issue. No additional workarounds are necessary if patching is applied.

Description

A vulnerability in h11's handling of HTTP/1.1 chunked transfer encoding allows malformed chunked bodies with incorrect trailing bytes to be accepted. This leniency can cause request smuggling when combined with a buggy proxy that parses chunked bodies differently, potentially enabling attackers to bypass security controls or steal session credentials. The issue is fixed in h11 version 0.15.0 and affects glances versions >=4.2.1 and <4.3.1_2.

Impact

This vulnerability enables HTTP request smuggling attacks under certain conditions where a vulnerable h11-based server is behind a proxy with a different chunked encoding parser bug. Attackers can craft requests that are interpreted differently by the proxy and server, potentially bypassing access controls or stealing session credentials. The CVSS score of 9.1 indicates critical impact with high confidentiality and integrity impact but no availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 09:00 UTC

Technical details

References

Community reviews

Related threats