CVE-2026-40264 | OpenBao up to 2.5.2 improper restriction of security token assignment (GHSA-p49j-v9wc-wg57)
VulDBArchived Apr 21, 2026✓ Full text saved
A vulnerability was found in OpenBao up to 2.5.2 . It has been declared as problematic . Affected by this issue is some unknown functionality. The manipulation results in improper restriction of security token assignment. This vulnerability is reported as CVE-2026-40264 . The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358393 · CVE-2026-40264 · GHSA-P49J-V9WC-WG57
OPENBAO UP TO 2.5.2 IMPROPER RESTRICTION OF SECURITY TOKEN ASSIGNMENT
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
2.6 $0-$5k 2.25+
Summaryinfo
A vulnerability was found in OpenBao up to 2.5.2. It has been rated as problematic. This affects an unknown part. This manipulation causes improper restriction of security token assignment. This vulnerability appears as CVE-2026-40264. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Detailsinfo
A vulnerability has been found in OpenBao up to 2.5.2 and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a improper restriction of security token assignment vulnerability. The CWE definition for the vulnerability is CWE-1259. The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected. As an impact it is known to affect availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-40264 since 04/10/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1134.001 for this issue.
Upgrading to version 2.5.3 eliminates this vulnerability.
Productinfo
Name
OpenBao
Version
2.5.0
2.5.1
2.5.2
Website
Product: https://github.com/openbao/openbao/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 2.7
VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Improper restriction of security token assignment
CWE: CWE-1259
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: OpenBao 2.5.3
Timelineinfo
04/10/2026 CVE reserved
04/21/2026 +11 days Advisory disclosed
04/21/2026 +0 days VulDB entry created
04/21/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-p49j-v9wc-wg57
Status: Confirmed
CVE: CVE-2026-40264 (🔒)
GCVE (CVE): GCVE-0-2026-40264
GCVE (VulDB): GCVE-100-358393
Entryinfo
Created: 04/21/2026 07:07
Changes: 04/21/2026 07:07 (66)
Complete: 🔍
Cache ID: 99:A10:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸