CVE-2026-61801: Openbao · `github
Affects openbaoSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.5.5-r2 when convenient.
Data as of 20 Nov 2026, 03:34 UTC
- Patch
- Available – fixed in 2.5.5-r2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade openbao to 2.5.5-r2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartopenbaopkg:apk/cleanstart/openbaoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade openbao to version 2.5.5-r2 or later to remediate this vulnerability. Since a patch is available, applying the official fix is the recommended mitigation.
Description
A medium severity security vulnerability (CVE-2026-61801) affects the openbao package versions prior to 2.5.5-r2. The flaw does not impact confidentiality or integrity but causes a high impact on availability. A patch is available in version 2.5.5-r2.