CVE-2026-119195VulnerabilityPublished 31 Oct 2026

Glances: pyasn1 has quadratic-time denial of service in constructed string and indefinite-length ANY decoding

Affects glancesSource GCVE Database

Compare

Authoritative record:CVE-2026-119195· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.3_1 or 3.1.6.2 soon.

Data as of 31 Oct 2026, 16:08 UTC

CVSS 3.1 base score

7.5High

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 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 29 Oct 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 30 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.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	Fixed in 3.1.6.2 4.3.3_1

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 and should be applied by upgrading to Glances versions 3.1.6.2 or 4.3.3_1 or later. The vendor advisory confirms these fixed versions. No additional mitigations are specified or required beyond applying the official fix.

Description

A denial of service vulnerability exists in pyasn1 versions 0.6.4 and earlier used by Glances, where decoding constructed OCTET STRING or character strings with many fragments causes quadratic CPU time consumption. This occurs due to inefficient string concatenation in BER and CER decoding paths, potentially allowing CPU exhaustion if attacker-controlled ASN.1 input is processed without limits. The issue affects multiple string types and indefinite-length ANY decoding. No confidentiality or integrity impact is reported. Fixed versions 3.1.6.2 and 4.3.3_1 address this issue.

Impact

An attacker who can supply crafted ASN.1 input to an application using the affected pyasn1 decoder can cause excessive CPU consumption due to quadratic-time string concatenation during decoding. This can lead to denial of service by exhausting CPU resources of the decoding worker. There is no impact on confidentiality or integrity. The severity is high with a CVSS v3.1 base score of 7.5, reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to availability.

Summary

In pyasn1 version 0.6.4 and earlier, the BER and CER decoders for constructed OCTET STRINGs, constructed character strings, and indefinite-length ANY types inefficiently concatenate fragments using repeated string appends. This results in quadratic time complexity relative to the number of fragments, causing disproportionate CPU usage during decoding. The vulnerability affects Glances versions >=3.0.2_1 <3.1.6.2 and >=4.3.1_1 <4.3.3_1, as well as >=4.5.0. The flaw does not impact confidentiality or integrity but can cause denial of service by exhausting CPU resources. The issue is distinct from a previous OID-related vulnerability fixed in 0.6.4. The problem is fixed in Glances versions 3.1.6.2 and 4.3.3_1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2026, 16:08 UTC

Technical details

References

Community reviews

Related threats