Skip to main content
CVE-2026-119195VulnerabilityPublished

S3ql: pyasn1 has quadratic-time denial of service in constructed string and indefinite-length ANY decoding

Affects s3qlSource GCVE Database

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

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

Data as of 31 Oct 2026, 16:36 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
Patch
Available – fixed in 3.8.1
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

Upgrade s3ql to 3.8.1.

Affected software

ProductAffectedFixed in
Homebrews3qlpkg:brew/s3qlOther threatsAffected
  • >=3.1 <3.8.1
  • >=6.0.0
Fixed in
  • 3.8.1

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 s3ql version 3.8.1. Users should upgrade to this version or later to remediate the vulnerability. No other mitigation or workaround is indicated by the vendor advisory.

Description

A denial of service vulnerability exists in pyasn1 versions 0.6.4 and earlier used by s3ql, where decoding constructed OCTET STRING or character strings with many fragments causes quadratic CPU time consumption due to inefficient string concatenation. This affects BER and CER decoding paths and can be triggered by attacker-supplied ASN.1 input, leading to CPU exhaustion without confidentiality or integrity impact. The issue is fixed in s3ql version 3.8.1.

References

Community reviews

Loading reviews…