VulnerabilityPublished 13 Aug 2026Updated 31 Oct 2026

CVE-2026-59884: Glances · pyasn1 BER/CER/DER decoder denial of service via unbounded long-form tag IDs

Affects glancesSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High · fixed in 4.5.5_1 : patch glances soon.

Data as of 1 Nov 2026, 01:38 UTC

CVSS 3.1 base score

7.5High

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

Patch: Available – fixed in 4.5.5_1, 4.3.3_1, 3.1.6.2

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 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 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 glances to 4.5.5_1, 4.3.3_1 or 3.1.6.2.

Affected software

Product	Affected	Fixed in
Homebrewglances`pkg:brew/glances`Other threats	Affected >=3.0.2_1 <3.1.6.2 >=4.3.1_1 <4.3.3_1 >=4.5.0.1 <4.5.5_1	Fixed in 3.1.6.2 4.3.3_1 4.5.5_1

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

AI-suggested

A fix is available in pyasn1 version 0.6.4 and corresponding Glances versions 3.1.6.2, 4.3.3_1, and 4.5.5_1. Users should upgrade to these fixed versions to remediate the vulnerability. As a workaround, users can bound the size of untrusted input passed to the decode() function to prevent excessive resource consumption.

Description

A denial of service vulnerability exists in the pyasn1 BER/CER/DER decoder used by the Glances product. The decoder processes long-form tag IDs without an upper bound, allowing crafted inputs to cause excessive CPU consumption or unhandled exceptions. This affects applications decoding untrusted BER/CER/DER inputs using pyasn1 versions before the fixed releases. The issue is fixed in pyasn1 version 0.6.4 and corresponding Glances versions.

Impact

This vulnerability allows denial of service via excessive CPU consumption when decoding crafted BER/CER/DER inputs, potentially causing application unavailability. Additionally, on Python 3.11+, unhandled exceptions may bypass error handling, which could affect application stability or error reporting. There is no impact on confidentiality or integrity.

Summary

The BER decoder in pyasn1, shared by CER and DER codecs, parses long-form tags by accumulating continuation octets in a loop without an upper bound on tag ID size. An attacker can craft input that forces the decoder to build an arbitrarily large integer, causing CPU usage to grow quadratically with input size, resulting in denial of service. On Python 3.11 and later, oversized tag IDs can also trigger unhandled ValueError exceptions during error message formatting, potentially bypassing caller error handling. The affected components include pyasn1.codec.ber.decoder, pyasn1.codec.cer.decoder, pyasn1.codec.der.decoder, and pyasn1.type.tag. The encoders and pyasn1.codec.native codec are not affected. The vulnerability is fixed in pyasn1 version 0.6.4 by limiting long-form tag IDs to 20 octets and rejecting oversized tags with PyAsn1Error. Tag ID rendering was also hardened against integer-to-string conversion limits.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 01:38 UTC

Technical details

References

Community reviews

Related threats