Skip to content
Fencer Intel
low 2.7

CVE-2026-40264 json

OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation

published 6mo ago modified last mo. also BIT-openbao-2026-40264 , EUVD-2026-24037 , GHSA-p49j-v9wc-wg57 , GO-2026-5526

cvss
2.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

OpenBao is an open source identity-based secrets management system. OpenBao's namespaces provide multi-tenant separation. Prior to version 2.5.3, a tenant who leaks token accessors can have their token revoked or renewed by a privileged administrator in another tenant. This is addressed in v2.5.3.

Patch / fix

  • go github.com/openbao/openbao 0.0.0-20260420162526-f58111d2ca54
  • bitnami openbao 2.5.3
  • openbao openbao 2.5.3
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • openbao openSUSE Tumbleweed 2.5.3-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:10594-1

  • openbao Alpine 3.24, Alpine 3.23 2.5.4-r0

alpine advisories ALPINE-CVE-2026-40264

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-40264 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-40264 updated cvss 5.8

OpenBao: OpenBao: Unauthorized token management by privileged administrator

  • Red Hat All currently supported Red Hat products
    not 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
none
Automatable
no
Technical impact
partial
Assessed
6mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 2.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA 4.0 2.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/openbao/openbao
<0.0.0-20260420162526-f58111d2ca54
0.0.0-20260420162526-f58111d2ca54
bitnami openbao
<2.5.3
2.5.3

Affected products

  • openbao openbao

Classification

Weakness
  • CWE-1259 Improper Restriction of Security Token Assignment

References

Sources

Fencer Intel 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.