VulnerabilityPublished 31 Oct 2026

CVE-2026-119196: Dvc · pyasn1 has quadratic CPU consumption in constructed BIT STRING decoding

Affects dvcSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-59885

Authoritative record:CVE-2026-119196· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 3.67.1_19 soon.

Data as of 31 Oct 2026, 16:21 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 3.67.1_19

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 dvc to 3.67.1_19.

Affected software

Product	Affected	Fixed in
Homebrewdvc`pkg:brew/dvc`Other threats	Affected >=1.4.0 <3.67.1_19	Fixed in 3.67.1_19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version of pyasn1 is available at 3.67.1_19 that resolves this vulnerability. Users should upgrade to version 3.67.1_19 or later to mitigate the issue.

Description

CVE-2026-119196 affects pyasn1 versions from 1.4.0 up to but not including 3.67.1_19. The vulnerability causes quadratic CPU consumption when decoding constructed BIT STRING values with many fragments, potentially leading to CPU exhaustion and denial of service. This occurs because the decoder repeatedly shifts and copies the accumulated value for each fragment. The issue affects BER and CER decoders and certain schema-driven DER decoding paths. No confidentiality or integrity impact is reported. A fix is available in version 3.67.1_19.

Impact

An attacker who can supply sufficiently large, constructed BIT STRING ASN.1 data to an affected pyasn1 decoder can cause excessive CPU consumption, potentially resulting in denial of service by exhausting the decoding thread or worker. This impact assumes the application automatically decodes untrusted ASN.1 input and does not impose input limits sufficient to block the attack. There is no demonstrated impact on confidentiality or integrity. The CVSS v3.1 base score is 7.5 (high) reflecting the denial of service potential via unauthenticated network input.

Summary

In pyasn1 through version 0.6.4 (and affected versions up to 3.67.1_19), decoding constructed BIT STRING values with many fragments causes CPU time to grow quadratically with input size. This is due to the decoder's method of repeatedly shifting and copying the accumulated bit string value for each fragment during BER and CER decoding, and in schema-driven DER decoding of definite-length constructed BIT STRINGs. The vulnerability can be triggered by attacker-controlled ASN.1 data, leading to CPU exhaustion during decode() calls without requiring any further processing of the decoded value. The decoder's nesting-depth and length octet limits do not prevent this attack. The vulnerability does not affect schema-less DER decoding, which rejects constructed BIT STRINGs. The issue is distinct from a previously fixed OBJECT IDENTIFIER accumulation vulnerability (CVE-2026-59885).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats