CVE-2026-104088
Published:October 12, 2026
Updated:October 13, 2026
Impact OpenBao's request handling mechanism did not validate operation type when non-HTTP API requests were created, such as with inline authentication and workflows. Certain internal operation types would result in token issues when handled as a login request. While these operations would by default not specify policies, identity entity resolution would still occur, potentially leading to attached policies on this token. All existing community-maintained plugins did not perform policy resolution on any internal operations and thus token scope would be limited. ### Patches This has been patched in v2.6.2. ### References Gia Bui (@yabeow) from Calif.io reported the inline auth problem and expanded impact was disclosed by @cipherboy.
Affected Packages
https://github.com/openbao/openbao.git (GITHUB):
Affected version(s) >=v2.4.0 <v2.6.2Fix Suggestion:
Update to version v2.6.2github.com/openbao/openbao (GO):
Affected version(s) >=v2.4.0 <v2.6.2Fix Suggestion:
Update to version v2.6.2github.com/openbao/openbao/v2 (GO):
Affected version(s) >=v2.6.0 <v2.6.2Fix Suggestion:
Update to version v2.6.2Related Resources (3)
Do you need more information?
Contact UsCVSS v4
Base Score:
9.2
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
PRESENT
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
HIGH
Vulnerable System Availability
HIGH
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
9.8
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Weakness Type (CWE)
Incorrect Authorization