CVE-2026-55776 json
OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types
published 2026-06-19 4 mo ago modified 2026-09-29 40 d ago also BIT-openbao-2026-55776 , EUVD-2026-78682 , GHSA-8w8f-r2xv-4q4j , GO-2026-5267
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/openbao/openbao 0.0.0-20260617104123-db57c62602b2
- bitnami openbao 2.5.5
- linuxfoundation openbao 2.5.5
- openbao openbao 2.5.5
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/openbao/openbao@bb17827 commit
- github.com/openbao/openbao@db57c62 commit
- github.com/openbao/openbao#3309 pull request
- github.com/openbao/openbao#3312 pull request
- github.com/openbao/openbao/releases/tag/v2.5.5 release
- github.com/openbao/openbao/releases/tag/v2.6.0 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-55776 updated cvss 6.5
github.com/openbao/openbao: OpenBao: Denial of Service via crafted key creation in transit secrets engine
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 52 d ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/openbao/openbao/security/advisories/GHSA-8w8f-r2xv-4q4j referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/openbao/openbao | >=0.1.0, <=2.5.4 <0.0.0-20260617104123-db57c62602b2 >=0.1.0 |
0.0.0-20260617104123-db57c62602b2 |
| bitnami | openbao | <2.5.5 |
2.5.5 |
Affected products
- openbao openbao
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
github.com
/openbao/openbao/pull/3309
web, patch
-
github.com
/openbao/openbao/pull/3312
web
-
github.com
/openbao/openbao/commit/bb17827f3e33779a10166f7d0e61b191c0facef9
web
-
github.com
/openbao/openbao/commit/db57c62602b25da12951f3f0edb888e7c4da61e5
web, patch
-
github.com
/openbao/openbao/security/advisories/GHSA-8w8f-r2xv-4q4j
exploit, web, advisory
-
github.com
/openbao/openbao/releases/tag/v2.5.5
web
-
github.com
/openbao/openbao/releases/tag/v2.6.0
web
-
github.com
/openbao/openbao
package
-
nvd.nist.gov
/vuln/detail/CVE-2026-55776
web
Sources
- CVE List CVE-2026-55776
- GitHub Advisory GHSA-8w8f-r2xv-4q4j
- NVD CVE-2026-55776
- OSV BIT-openbao-2026-55776
- OSV GO-2026-5267
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.