cve.bz

CVE-2026-40264 openbao openbao

2.0 lowEPSS 0.3%Fix available

Low (2.0) in openbao openbao. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/openbao/openbao 0.0.0-20260420162526-f58111d2ca54.

On this page
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.

Severity

CVSS 4.0

2.0 low
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

CVSS 3.1

2.7 low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1259 Improper Restriction of Security Token Assignment
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40264 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40264?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40264?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40264 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openbao:openbaobefore 2.5.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p49j-v9wc-wg57Gogithub.com/openbao/openbao<0.0.0-20260420162526-f58111d2ca540.0.0-20260420162526-f58111d2ca54
GO-2026-5526Gogithub.com/openbao/openbao<0.0.0-20260420162526-f58111d2ca540.0.0-20260420162526-f58111d2ca54

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedopenbao2.5.3-1.1openSUSE-SU-2026:10594-1
Alpinev3.23, v3.24openbao2.5.4-r0ALPINE-CVE-2026-40264

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE · Alpine.

Attack patterns (CAPEC)

  • CAPEC-121 Exploit Non-Production Interfaces Likelihood: Low · Severity: High
  • CAPEC-681 Exploitation of Improperly Controlled Hardware Security Identifiers Likelihood: Medium · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON