Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-34580 high CVSS 7.5

Vulnerability in Botan is a C++ cryptography library. In (CVE-2026-34580)

Summary

Vulnerability in Botan is a C++ cryptography library. In (CVE-2026-34580). Data can be tampered with by attackers. Mitigation: upgrade to 3.11.1 or later.

Original description

The description as published by the source.

Botan is a C++ cryptography library. In 3.11.0, the function Certificate_Store::certificate_known had a misleading name; it would return true if any certificate in the store had a DN (and subject key identifier, if set) matching that of the argument. It did not check that the cert it found and the cert it was passed were actually the same certificate. In 3.11.0 an extension of path validation logic was made which assumed that certificate_known only returned true if the certificates were in fact identical. The impact is that if an end entity certificate is presented, and its DN (and subject key identifier, if set) match that of any trusted root, the end entity certificate is accepted immediately as if it itself were a trusted root. , This vulnerability is fixed in 3.11.1.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-34580 has been found in Botan is a C++ cryptography library. In.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade Botan is a C++ cryptography library. In to 3.11.1 or later.
If unsure, ask your IT team or search "Botan is a C++ cryptography library. In CVE-2026-34580" on the vendor's site.

CVE-2026-34580 (Botan is a C++ cryptography library. In) — CWE-295 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.11.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-295) exists in Botan is a C++ cryptography library. In.

📍 Affected scope

Check the vendor advisory for the affected versions of Botan is a C++ cryptography library. In.

🔥 Severity

Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 3.11.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Botan is a C++ cryptography library. In を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade Botan is a C++ cryptography library. In to 3.11.1

    ステージング環境で 3.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details