Quick answers
- Is CVE-2026-104267 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104267 being exploited in the wild.
- How severe is CVE-2026-104267?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- Botan Project Botan 2.7.0 to 3.12.x.
- Is there a fix for CVE-2026-104267?
- Yes: fixed in 3.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104267 attacked?
- It is attacked over the network or with local access.
- Am I affected by CVE-2026-104267?
- Check whether you run Botan Project Botan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.13.0
Technical details
The vulnerability is an integer overflow in unchecked multiplication when calculating Scrypt memory allocation on 32-bit platforms; attacker-controlled Scrypt parameters wrap the allocation size, resulting in a heap buffer smaller than the algorithm requires, causing ~4 GB of output to be written past the buffer boundary. The issue affects systems with Scrypt enabled that accept arbitrary parameters from untrusted sources, including password key derivation with user-supplied encrypted keys. The fix in version 3.13.0 introduces memory bounds checking (2 GB for 32-bit, 8 GB elsewhere) and uses safe integer arithmetic (checked_mul/checked_add).
Affected products
- Botan Project Botan 2.7.0 to 3.12.x
Timeline
- 2026-11-06: disclosed
- 2026-05-30: patched: Fix merged in version 3.13.0