CVE-2026-23490: pyasn1 has a DoS vulnerability in decoder
pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.2, a Denial-of-Service issue has been found that leads to memory exhaustion from malformed RELATIVE-OID with excessive continuation octets. This vulnerability is fixed in 0.6.2.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23490 is a denial-of-service flaw in the Python pyasn1 library. Malformed ASN.1 data can trigger excessive memory use and make an affected application unavailable. The issue affects pyasn1 versions before 0.6.2 and is fixed in 0.6.2.
Executive priority
Prioritize remediation for internet-facing or message-processing services that parse ASN.1 with pyasn1. This is not described as code execution, but it can cause service outage and should be handled in normal high-severity patch cycles.
Technical view
pyasn1 before 0.6.2 can exhaust memory while decoding malformed RELATIVE-OID values containing excessive continuation octets. The CVSS 3.1 score is 7.5, reflecting network attackability, low complexity, no required privileges or user interaction, and availability impact only.
Likely exposure
Exposure is most likely in Python applications or packaged platforms that include pyasn1 below 0.6.2 and decode ASN.1 data from untrusted or remotely supplied sources. The bundle also cites Debian LTS and multiple Red Hat advisories, indicating downstream distribution relevance.
Exploitation context
The provided bundle does not cite active exploitation, and KEV is false. Public evidence supports a remotely triggerable availability issue, but not confidentiality impact, integrity impact, or confirmed in-the-wild exploitation.
Researcher notes
Focus review on dependency reachability: whether attacker-controlled ASN.1 reaches pyasn1 decoder code. Sources identify RELATIVE-OID decoding and excessive continuation octets as the memory-exhaustion condition, with upstream commit and v0.6.2 release cited as the fix.
Mitigation direction
Upgrade pyasn1 to version 0.6.2 or later.
Apply Debian or Red Hat vendor updates where pyasn1 is OS-packaged.
Check vendor guidance for downstream products that bundle pyasn1.
Limit exposure of ASN.1 decoding paths that accept untrusted input until patched.
Validation and detection
Inventory Python dependencies for pyasn1 versions below 0.6.2.
Check OS package advisories for installed pyasn1 packages.
Identify applications that decode ASN.1 data using pyasn1.
Confirm patched hosts or builds use pyasn1 0.6.2 or vendor-fixed packages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.