CVE-2026-104267 · Package
NO FIX YET · SEE WHAT TO DO
Botan's Scrypt code on 32-bit platforms miscalculates buffer size from attacker-chosen parameters, so a crafted parameter set writes about four gigabytes past a heap buffer. The likely result is a crash (denial of service); code execution is described as difficult but not ruled out.
first public Sep 1, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only applications that use Botan's Scrypt on 32-bit platforms and accept Scrypt parameters from a hostile source, such as decrypting attacker-supplied encrypted keys. Systems that use Scrypt only with trusted parameters, or run on 64-bit platforms, are not exposed. unknown whether other paths are affected.
Not affected if 64-bit-only, scrypt-unused, trusted-scrypt-parameters
Who cares 32-bit, botan, c++, cryptography
botan version or the lockfile or package manifest, and look for anything from 2.7.0 up to 3.12.x.3.13.0Botan 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.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.