CVE-2026-32877
Heap over-read in Botan SM2 decryption can crash app.
Is CVE-2026-32877 being exploited?
Not confirmed. CVE-2026-32877 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-32877?
CVE-2026-32877 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32877?
Yes. A fix has been recorded for CVE-2026-32877. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32877 affect?
CVE-2026-32877 affects Botan 2.3.0 - 3.10.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32877?
Upgrade to Botan 3.11.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap over-read up to 31 bytes during SM2 decryption may crash process; undefined behavior. Patch in 3.11.0.
Patch when possible
- affected>= 2.3.0 and < 3.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.