CVE-2026-32883
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBotan 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Botan versions 3.0.0 through 3.10.x, the X509 path validation logic checked OCSP response status codes but failed to verify the OCSP response signature itself, allowing potential forging of certificate status responses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Botan library versionQuery the Botan library version at runtime via its version function (e.g., Botan::version_major(), Botan::version_minor(), Botan::version_patch()) or check the library binary/header file for the version string. If using a package manager, run 'pkg-config --modversion botan3' or equivalent for your distribution.Affected if The installed version is 3.0.0 through 3.10.x (any version before 3.11.0)
-
Locate the Botan library file in useFind the actual Botan library file loaded by your application using 'ldd <application>' on Linux or by checking the linked libraries in your build configuration. Note the full path to the specific Botan library binary being used.Affected if The located library file corresponds to a version below 3.11.0
-
Determine if OCSP validation is enabled in your X509 configurationReview your application's X509 certificate validation configuration or code to check whether OCSP (Online Certificate Status Protocol) checking is enabled. Look for OCSP-related options such as 'allow ocsp', 'check ocsp', or similar settings in your validation policy.Affected if OCSP checking is enabled and your validation policy requests OCSP status information for certificates
-
Verify if OCSP responses are being processedEnable debug or trace logging for your certificate validation path and observe whether OCSP requests are being made and responses received during X509 path validation. Check application logs for OCSP-related activity.Affected if Your application processes OCSP responses during certificate chain validation with an affected Botan version
You are affected if your environment uses a Botan library version between 3.0.0 and 3.10.x AND your application performs OCSP checking during X509 certificate validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.11.0
Upgrade Botan to version 3.11.0 or later to incorporate the patch that adds OCSP response signature verification.
Botan 3.11.0
- 1. Identify the current Botan library version in use by checking project dependencies or the installed library version
- 2. Upgrade the Botan library to version 3.11.0 or later (e.g., using package manager like apt, yum, or rebuilding from source)
- 3. Verify the upgrade was successful by confirming the installed Botan version
- 4. Test that OCSP response signature verification is now functioning correctly during X509 path validation
- 5. Rebuild and redeploy any applications that link against the Botan library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32883 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32883 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data