Skip to main content
VulnerabilityPublished

CVE-2026-119194: Smbclient ng · pyasn1 has quadratic CPU use in schemaless BER/CER/DER container decoding

Affects smbclient-ngSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119194· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 31 Oct 2026, 15:54 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.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
Homebrewsmbclient-ngpkg:brew/smbclient-ngOther threatsAffected
  • >=3.1.0
Fixed in–

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

AI-suggested

The described fix stops the growth of the classification set after two distinct tag sets are detected, mitigating the CPU exhaustion. Until an official patch is available, avoid passing untrusted or attacker-controlled BER, CER, or DER data to schemaless decoding routines in pyasn1.

Description

CVE-2026-119194 is a high-severity vulnerability in pyasn1 used by smbclient-ng (>=3.1.0) where schemaless decoding of BER, CER, or DER data with many distinct long tag IDs causes quadratic CPU usage. This can lead to CPU exhaustion and reduced service availability when processing attacker-controlled inputs. The vulnerability arises from inefficient handling of tag sets during decoding, causing excessive CPU consumption without affecting confidentiality or integrity.

References

Community reviews

Loading reviews…