Skip to content
Fencer Intel
critical 9.2

CVE-2026-118769 json

Botan: Integer overflow when reporting block size in FFI can cause memory corruption

published 11d ago modified 10d ago also EUVD-2026-113278

cvss
9.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

Botan is a C++ cryptography library. From 2.1.0 until 3.13.0, the Botan C API function botan_block_cipher_block_size converted a size_t block size to int without a bounds check. In an application that accepts external algorithm parameter strings and uses the FFI raw ECB mode, an attacker can select the variable-block-size Lion cipher so that the reported size is truncated, the caller allocates insufficient memory, and later block processing causes memory corruption. The C++ API and normally used C API modes such as CBC and CTR are unaffected. This issue is fixed in version 3.13.0.

Patch / fix

  • botan_project botan 3.13.0
  • botan3 Debian 14 3.13.0+dfsg-2

debian advisories DEBIAN-CVE-2026-118769

Is CVE-2026-118769 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-118769 updated cvss 8.1

botan: Botan: Integer overflow when reporting block size in FFI can cause memory corruption

  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-27/hub-rhel9 Red Hat Enterprise Linux 9 rust-sequoia-sq 1.4.0.2-2.el10 Red Hat Enterprise Linux 10 rust-sequoia-sq 1.4.0.2-2.el10, rust-sequoia-sqv 1.3.0-2.el10_0, rust-podman-sequoia 0.4.0~pqc.3-1.el10_2
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Hardened Images rust-podman-sequoia 0.4.0~pqc.3-1.el10_2
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
11d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • randombit botan

Classification

Weakness
  • CWE-125 Out-of-bounds Read
  • CWE-681 Incorrect Conversion between Numeric Types
  • CWE-787 Out-of-bounds Write

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.