CVE-2026-32877: 
Botan vulnerability analysis and mitigation

CVE-2026-32877 is a heap buffer over-read vulnerability in the Botan C++ cryptography library affecting SM2 decryption operations. During SM2 decryption, the authentication code value (C3) validation logic fails to verify that the encoded value is of the expected length before performing a comparison, allowing an invalid ciphertext to trigger a heap over-read of up to 31 bytes. The vulnerability affects Botan versions 2.3.0 through 3.10.x and was patched in version 3.11.0. It carries a CVSS v3.1 base score of 8.2 (High), reflecting its network-accessible, no-authentication-required attack surface (GitHub Advisory).

The root cause is classified as CWE-125 (Out-of-bounds Read). During SM2 decryption, the C3 authentication code field is read and compared without first validating that its encoded length matches the expected size. An attacker supplying a crafted ciphertext with an undersized C3 hash field causes the library to read up to 31 bytes beyond the intended buffer boundary on the heap. This is exploitable remotely with no privileges or user interaction required, making it particularly dangerous in contexts where servers process attacker-controlled SM2 ciphertexts — such as Chinese standards-compliant TLS (TLCP), payment systems, and enterprise applications (GitHub Advisory).

Successful exploitation can cause a process crash (denial of service) due to the heap over-read, or trigger undefined behavior that may result in partial disclosure of heap memory contents. The confidentiality impact is rated Low, as up to 31 bytes of adjacent heap memory could potentially be leaked, while availability impact is rated High due to the likelihood of a crash. Any application using Botan's SM2 decryption functionality — including TLCP-compliant servers, payment systems, and enterprise applications — is within scope (GitHub Advisory).

1. Identify target: Locate network-accessible services using Botan versions 2.3.0–3.10.x for SM2 decryption, such as TLCP-compliant TLS servers, payment gateways, or enterprise applications.
2. Craft malicious ciphertext: Construct an SM2-formatted ciphertext where the C3 authentication code field is encoded with a length shorter than the expected hash output size (e.g., fewer than the required bytes for the hash algorithm in use).
3. Transmit the payload: Send the crafted ciphertext to the target service over the network — no authentication or user interaction is required.
4. Trigger heap over-read: The Botan SM2 decryption routine reads the undersized C3 field without length validation, causing a heap over-read of up to 31 bytes beyond the buffer boundary.
5. Achieve objective: The over-read results in a process crash (DoS) or, in some memory layouts, may expose adjacent heap contents containing sensitive data (GitHub Advisory).

• Network: Unexpected or malformed SM2/TLCP handshake traffic directed at services using Botan; repeated connection attempts with non-standard ciphertext structures.
• Logs: Application crash logs or core dumps originating from Botan's SM2 decryption code path; segmentation fault or heap corruption error messages in service logs.
• Process: Unexpected termination (crash) of services that use Botan for SM2 decryption; increased process restart frequency for affected services.
• File System: Core dump files generated by the affected process in the working directory or system crash dump location.

The primary remediation is to upgrade Botan to version 3.11.0 or later, which includes the fix for this vulnerability (GitHub Advisory). If immediate patching is not feasible, organizations should limit network exposure of services using Botan's SM2 decryption functionality through network segmentation, firewall rules, and access controls to restrict which clients can submit ciphertexts. Monitoring for unexpected application crashes or abnormal behavior in systems using Botan is also recommended as a compensating control.

The vulnerability was reported by researcher HarutoKimura and disclosed via GitHub Security Advisories on March 29–30, 2026 (GitHub Advisory). Coverage appeared on security aggregation platforms and the Solus Linux community forum noted it in a weekly security roundup (Solus Forum). German Linux security outlet Pro-Linux also covered multiple Botan 3 issues including this CVE (Pro-Linux). Community reaction has been measured, consistent with a library-level vulnerability with no active exploitation.