OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.
CVE-2026-55776
MEDIUMPre-NVD 6.56.5—Elevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
September 17, 2026
Advisory Details (5)
Auto-updated Sep 15, 2026Patch available. Sources: github, github_pr, github_commit.
github_commit
commit db57c62602b2 (openbao/openbao)
Fix landed in openbao/openbao commit db57c62602b2 — awaiting tagged release
https://github.com/openbao/openbao/commit/db57c62602b25da12951f3f0edb888e7c4da61e5github_commit
commit bb17827f3e33 (openbao/openbao)
Fix landed in openbao/openbao commit bb17827f3e33 — awaiting tagged release
https://github.com/openbao/openbao/commit/bb17827f3e33779a10166f7d0e61b191c0facef9github_pr
Fix panic due to unlock of unlocked mutex in Transit (#3309)
Fix merged in openbao/openbao PR #3312 on 2026-06-17 — awaiting tagged release
https://github.com/openbao/openbao/pull/3312github_pr
Fix panic due to unlock of unlocked mutex in Transit
Fix merged in openbao/openbao PR #3309 on 2026-06-17 — awaiting tagged release
https://github.com/openbao/openbao/pull/3309github Patch Available
OpenBao crashes on Transit engine key creation with derived=true for RSA key types · Advisory · openbao/openbao · GitHub
https://github.com/openbao/openbao/security/advisories/GHSA-8w8f-r2xv-4q4jVendor Advisories for CVE-2026-55776(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/openbao/openbao | — | 0.0.0-20260617104123-db57c62602b2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 18:16 UTCEG score recompute
- 2026-09-17 15:44 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 16:36 UTCEG score recompute
- 2026-07-31 04:43 UTCEG score recompute
- 2026-07-26 16:46 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-06-19 22:24 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-55776?
CVE-2026-55776 is a medium vulnerability published on June 19, 2026. OpenBao is an open source identity-based secrets management system. Prior to 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy…
When was CVE-2026-55776 disclosed?
CVE-2026-55776 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55776 actively exploited?
CVE-2026-55776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-55776?
CVE-2026-55776 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-55776?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55776, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55776
Is Your Infrastructure Affected by CVE-2026-55776?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.