Is CVE-2026-34580 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34580 being exploited in the wild.

How severe is CVE-2026-34580?

High severity, with a CVSS score of 7.5, published 7 April 2026.

Which products and versions are affected?

randombit Botan 3.11.0; Red Hat Red Hat Enterprise Linux 10 unspecified.

Is there a fix for CVE-2026-34580?

A patch was published on 2026-04-07: Fixed in version 3.11.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34580 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34580?

Check whether you run Botan Project Botan. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34580: Botan certificate validation bypass in Certificate_Store

CVE-2026-34580 · Severity: high · CVSS 7.5 · Published 2026-04-07

Botan is a widely used software library that provides cryptographic functions like encryption and digital certificate verification. A flaw in how the library checks trusted certificates allows a malicious certificate to be incorrectly accepted as a trusted authority. This could allow an attacker to impersonate legitimate services or intercept secure communications without triggering security warnings.

Technologies: Botan Project Botan. Vendors: Botan Project.

Quick answers

Is CVE-2026-34580 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34580 being exploited in the wild.
How severe is CVE-2026-34580?: High severity, with a CVSS score of 7.5, published 7 April 2026.
Which products and versions are affected?: randombit Botan 3.11.0; Red Hat Red Hat Enterprise Linux 10 unspecified.
Is there a fix for CVE-2026-34580?: A patch was published on 2026-04-07: Fixed in version 3.11.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34580 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34580?: Check whether you run Botan Project Botan. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A certificate validation bypass exists in Botan 3.11.0 due to trust anchor confusion in the Certificate_Store::certificate_known function. The function incorrectly returned a success boolean if a certificate's Distinguished Name (DN) and Subject Key Identifier (SKI) matched an entry in the trusted store, without verifying that the actual certificate data was identical. Combined with new path validation logic in version 3.11.0, this allows an end-entity certificate to be treated as a trusted root if its metadata matches a known root. An unauthenticated remote attacker can exploit this to bypass X.509 chain validation. The issue is resolved in Botan version 3.11.1.

Affected products

randombit Botan 3.11.0
Red Hat Red Hat Enterprise Linux 10 unspecified

Timeline

2026-04-07: disclosed
2026-04-07: advisory
2026-04-07: patched: Fixed in version 3.11.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.