Botan: scrypt V-buffer heap overflow on 32-bit from constructor-accepted parameters
- Exploited
- No known exploitation
- Fix
- Fixed in 3.13.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.13.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 4/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Botan, a C++ cryptography library, has a heap buffer overflow in its scrypt implementation on 32-bit platforms in earlier releases, where attacker-chosen parameters can wrap a memory size calculation and write about four gigabytes past a too-small buffer. A local attacker with low privileges can trigger it when a user takes an action such as decrypting an attacker-supplied private key, crashing the process for denial of service, though code execution is not demonstrated and cannot be ruled out.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Botan is a C++ cryptography library. From 2.7.0 until 3.13.0, Botan's Scrypt implementation on 32-bit platforms computes required memory with unchecked multiplication, allowing attacker-controlled Scrypt parameters to wrap the allocation size and create a buffer smaller than the algorithm subsequently writes. The issue affects systems that enable Scrypt and accept arbitrary parameters from a hostile source, including applications that decrypt attacker-supplied encrypted private keys. A triggering parameter set can cause approximately four gigabytes of Scrypt output to be written past the allocated heap buffer, immediately crashing the process and causing denial of service. Arbitrary code execution is not demonstrated and appears difficult, but cannot be excluded from the overwrite primitive. This issue is fixed in version 3.13.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.1/10CVSS 4.1
- No patch0/5No signal
What would change the score
- Would score about 59 if added to CISA KEV
- Would score about 54 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.13.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- randombit botan
From 2.7.0 · fixed in 3.13.0
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104267
Is CVE-2026-104267 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-104267?
botan: from 2.7.0 before 3.13.0.Source: cve.now feed data
How do I fix CVE-2026-104267?
Upgrade to a fixed version: 3.13.0.Source: cve.now feed data