VulnerabilityPublished 13 Aug 2026Updated 31 Oct 2026

CVE-2026-30922: Molecule · Denial of Service in pyasn1 via Unbounded Recursion

Affects moleculeSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 26.3.0_1 or 3.0.5 soon.

Data as of 1 Nov 2026, 01:50 UTC

CVSS 3.0 base score

7.5High

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

Patch: Available – fixed in 26.3.0_1, 3.0.5

CVSS:3.0/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 molecule to 26.3.0_1 or 3.0.5.

Patches and advisories

Affected software

Product	Affected	Fixed in
Homebrewmolecule`pkg:brew/molecule`Other threats	Affected >=1.17.3 <3.0.5 >=25.7.0 <26.3.0_1	Fixed in 3.0.5 26.3.0_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 pyasn1 to versions 3.0.5 or 26.3.0_1 or later. The vendor advisory confirms the availability of this fix. No additional mitigation steps are required once the update is applied. Users should ensure that all affected systems are updated promptly to prevent exploitation.

Description

The pyasn1 library suffers from a Denial of Service vulnerability due to unbounded recursion when decoding ASN.1 data with deeply nested indefinite-length SEQUENCE or SET structures. An attacker can craft a payload that triggers recursive decoding calls without depth limits, causing the Python interpreter to crash with a RecursionError or exhaust memory, leading to service crashes or resource exhaustion. This affects services using pyasn1 for ASN.1 parsing such as LDAP, SNMP, Kerberos, and X.509 parsers. The vulnerability is fixed in pyasn1 versions 3.0.5 and 26.3.0_1.

Impact

This vulnerability allows remote attackers to cause a Denial of Service by crashing the service process or exhausting server memory with a small crafted ASN.1 payload. Services using pyasn1 to parse untrusted ASN.1 data (e.g., LDAP, SNMP, Kerberos, X.509) can be disrupted. The attack leads to unhandled runtime exceptions (RecursionError) or out-of-memory conditions, terminating worker processes or threads and potentially affecting server stability. The resource exhaustion scales linearly with nesting depth, enabling significant memory consumption with relatively small payloads.

References

Community reviews

Loading reviews…