Skip to main content

Botan EUVDEUVD-2026-17211

| CVE-2026-32883 MEDIUM
Improper Verification of Cryptographic Signature (CWE-347)
2026-03-30 GitHub_M
5.9
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Impact

The CVSS 5.9 score with AV:N/AC:H reflects moderate severity with network accessibility but high complexity due to the need for specific network positioning. EPSS data is not provided, but the missing signature verification is a critical control bypass. The vulnerability is not confirmed as actively exploited (KEV status not provided), and no public exploit code has been identified in the available intelligence. However, the impact is significant: integrity is rated as HIGH (I:H), meaning an attacker can modify certificate status information. The high complexity requirement (AC:H) stems from the need to intercept or influence OCSP responses, limiting real-world exploitation but not eliminating it-particularly in enterprise or ISP-level attack scenarios. This is a genuine priority for applications relying on OCSP validation; it is not a low-real-risk high-CVSS case. Organizations using Botan for PKI operations should treat this as critical.

Exploit ScenarioDerived

An attacker positioned on the network path between a Botan application and an OCSP responder could intercept OCSP requests and respond with a forged response claiming a revoked certificate is 'good', bypassing revocation checks. No signature verification means the fraudulent response is accepted as legitimate. This could allow use of a compromised or revoked TLS certificate in encrypted sessions, potentially enabling man-in-the-middle attacks or impersonation. Attack complexity is high because the attacker must intercept network traffic or compromise the OCSP responder, but the scenario is realistic in corporate networks or ISP-level compromises. No public exploit code has been identified at the time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 30, 2026

Botan cryptography library versions 3.0.0 through 3.10.x fail to verify OCSP response signatures during X.509 certificate path validation, allowing attackers to forge certificate status responses and potentially bypass revocation checks. This integrity bypass affects any application using Botan for TLS or certificate validation and requires network positioning but not authentication. The vulnerability was patched in version 3.11.0.

RemediationAI

Upgrade Botan to version 3.11.0 or later immediately. This release includes the signature verification fix for OCSP responses. Users unable to upgrade should disable OCSP validation temporarily if feasible, though this weakens revocation checking and is not a long-term solution. Patch availability is confirmed; Botan 3.11.0 contains the upstream fix. Consult the GitHub security advisory at https://github.com/randombit/botan/security/advisories/GHSA-9j2j-hqmc-hf5x for detailed guidance and version-specific deployment notes.

Affected VersionsENISA

Botan 3.0.0, < 3.11.0

Affected Packages

euvd botan_3_0_0 fix: 3.11.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Botan is a C++ cryptography library widely used for TLS, PKI, and cryptographic operations. During X.509 path validation, the library processes OCSP (Online Certificate Status Protocol) responses to determine whether certificates have been revoked. The vulnerability stems from a missing cryptographic signature verification step (CWE-347: Improper Verification of Cryptographic Signature). While Botan correctly checked that OCSP responses contained an appropriate status code (e.g., 'good', 'revoked', 'unknown'), it did not validate the OCSP response's digital signature, which authenticates the response's origin and integrity. An attacker positioned to intercept or manipulate OCSP responses could craft fraudulent responses with valid-looking status codes, making revoked certificates appear valid.

Know when Botan gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Red Hat 6.8 MEDIUM

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
3.11.0
CVE Published
Mar 30, 2026 - 20:36 nvd
MEDIUM 5.9

DescriptionGitHub Advisory

Botan is a C++ cryptography library. From version 3.0.0 to before version 3.11.0, during X509 path validation, OCSP responses were checked for an appropriate status code, but critically omitted verifying the signature of the OCSP response itself. This issue has been patched in version 3.11.0.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Botan

View all
CVE-2016-2195 CRITICAL
9.8 May 13

Integer overflow in the PointGFp constructor in Botan before 1.10.11 and 1.11.x before 1.11.27 allows remote attackers t

CVE-2016-2196 CRITICAL
9.8 May 13

Heap-based buffer overflow in the P-521 reduction function in Botan 1.11.x before 1.11.27 allows remote attackers to cau

CVE-2017-2801 MEDIUM POC
6.5 May 24

A programming error exists in a way Randombit Botan cryptographic library version 2.0.1 implements x500 string compariso

CVE-2024-50383 MEDIUM POC
5.9 Oct 23

Botan before 3.6.0, when certain GCC versions are used, has a compiler-induced secret-dependent operation in lib/utils/d

CVE-2024-50382 MEDIUM POC
5.9 Oct 23

Botan before 3.6.0, when certain LLVM versions are used, has compiler-induced secret-dependent control flow in lib/utils

CVE-2021-40529 MEDIUM POC
5.9 Sep 06

The ElGamal implementation in Botan through 2.18.1, as used in Thunderbird and other products, allows plaintext recovery

CVE-2018-12435 MEDIUM POC
5.9 Jun 15

Botan 2.5.0 through 2.6.0 before 2.7.0 allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of

CVE-2015-7826 CRITICAL
9.8 Apr 10

botan 1.11.x before 1.11.22 improperly handles wildcard matching against hostnames, which might allow remote attackers t

CVE-2016-6878 CRITICAL
9.8 Apr 10

The Curve25519 code in botan before 1.11.31, on systems without a native 128-bit integer type, might allow attackers to

CVE-2016-9132 CRITICAL
9.8 Jan 30

In Botan 1.8.0 through 1.11.33, when decoding BER data an integer overflow could occur, which would cause an incorrect l

CVE-2021-24115 CRITICAL
9.8 Feb 22

In Botan before 2.17.3, constant-time computations are not used for certain decoding and encoding operations (base32, ba

CVE-2018-9127 CRITICAL
9.8 Apr 02

Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as v

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy