VulnerabilityPublished 31 Oct 2026

CVE-2026-119197: Glances · pyasn1 has quadratic-complexity denial of service in binary REAL decoding

Affects glancesSource GCVE Database

Compare

Authoritative record:CVE-2026-119197· 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 fix is available in pyasn1 version 0.6.5, which replaces the inefficient decoding loop with a more efficient implementation. Users should upgrade to pyasn1 0.6.5 or later to remediate this issue. Until upgrading, applications should reject or strictly limit ASN.1 input containing REAL values, especially large mantissas, before passing it to pyasn1 decoders. The appropriate input size limit depends on the application's CPU resources and expected request volume.

Description

CVE-2026-119197 is a denial of service vulnerability in pyasn1 versions up to 0.6.4 used by Glances. It arises from a quadratic-complexity loop in decoding binary-encoded ASN.1 REAL values with large mantissas, causing excessive CPU consumption. The flaw affects BER, CER, and DER decoders. An attacker supplying crafted ASN.1 REAL data to an affected decoder can cause CPU exhaustion during decoding. The issue is fixed in pyasn1 0.6.5. Users should upgrade to this version or apply input restrictions to mitigate the risk.

Impact

The vulnerability allows an attacker to cause CPU exhaustion on one core by supplying ASN.1 REAL values with large mantissas to the vulnerable pyasn1 decoders. This results in denial of service through excessive CPU consumption during decoding. The impact is limited to applications that decode attacker-controlled ASN.1 REAL values without input size restrictions. There is no direct impact on confidentiality or integrity. The vulnerability does not inherently expose network endpoints or allow unauthenticated exploitation; it requires the attacker to influence input to the decoder.

Summary

In pyasn1 versions 0.6.4 and earlier, the decoding of binary-encoded ASN.1 REAL values with large mantissas involves a loop that shifts and slices the mantissa byte string one octet at a time. This results in CPU time growing quadratically with the mantissa size. The vulnerability affects the BER, CER, and DER decoders since they share the same RealPayloadDecoder. An attacker able to supply ASN.1 data containing a REAL value to an application using these decoders can cause significant CPU exhaustion during the decode() operation, even without further processing of the decoded REAL object. The flaw is present in all releases from v0.2.1 through v0.6.4. The fix in pyasn1 0.6.5 replaces the inefficient loop with a single int.from_bytes conversion, preserving decoding correctness while eliminating the quadratic complexity. The advisory includes reproduction code demonstrating CPU time increasing roughly fourfold when doubling the mantissa size. The vulnerability does not imply network exposure or unauthenticated access by itself; it depends on the application passing attacker-controlled ASN.1 REAL values to the vulnerable decoder.

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