VulnerabilityPublished 13 Aug 2026Updated 31 Oct 2026

CVE-2026-23490: Glances · pyasn1 has a DoS vulnerability in decoder

Affects glancesSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.2 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.3.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.3.2.

Patches and advisories

Affected software

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

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 Glances version 4.3.2. Users should upgrade to this version or later to remediate the vulnerability. The vendor advisory confirms the availability of an official patch. No alternative mitigations or workarounds are specified.

Description

A Denial-of-Service (DoS) vulnerability exists in pyasn1 version 0.6.1 used by Glances, caused by memory exhaustion when decoding malformed RELATIVE-OID values with excessive continuation octets. This can cause systems processing ASN.1 data, such as LDAP servers or TLS/SSL endpoints, to hang or stop services due to resource exhaustion. A proof-of-concept demonstrates how crafted payloads trigger this condition. The issue is fixed in Glances version 4.3.2.

Impact

Successful exploitation results in denial of service due to memory exhaustion, causing affected systems to hang or crash. This impacts availability but does not affect confidentiality or integrity. Systems that parse ASN.1 data, including LDAP servers, TLS/SSL endpoints, and OCSP responders, are at risk of service disruption.

Summary

The pyasn1 library version 0.6.1 contains a DoS vulnerability (CVE-2026-23490) in its BER decoder, specifically in the handling of RELATIVE-OID values. Malformed RELATIVE-OID inputs with excessive continuation octets cause the decoder to consume excessive memory, leading to memory exhaustion and potential service disruption. This affects applications that decode ASN.1 data, including LDAP servers, TLS/SSL endpoints, and OCSP responders. The vulnerability is exploitable by an attacker supplying maliciously crafted ASN.1 data, such as a malicious X.509 certificate. A patch is available in Glances version 4.3.2 and related pyasn1 updates.

References

Community reviews

Loading reviews…