Skip to main content
VulnerabilityPublished

CVE-2026-35201: davidfstr rdiscount · Out-of-bounds Read

Affects davidfstr rdiscountSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.2.7.4 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.7.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Apr 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 davidfstr rdiscount to 2.2.7.4.

Affected software

ProductAffectedFixed in
davidfstrrdiscountAffected
  • >=1.3.1.1 <2.2.7.4
Fixed in
  • 2.2.7.4

AI-suggested

Upgrade rdiscount to version 2.2.7.4 or later, where this vulnerability is fixed. Since the vendor advisory does not provide additional remediation details, applying this official fix is the recommended action. Patch status is confirmed by the version fix information in the description.

Description

CVE-2026-35201 is an out-of-bounds read vulnerability in the rdiscount Markdown parser (versions >= 1.3.1.1 and < 2.2.7.4). It arises from a signed length truncation bug where inputs larger than INT_MAX are truncated before parsing, causing the parser to read beyond the buffer and potentially crash. This issue affects availability but does not impact confidentiality or integrity. The vulnerability is fixed in version 2.

References

Community reviews

Loading reviews…