Skip to main content
VulnerabilityPublished

CVE-2026-115365: openbao · Incorrect Authorization

Affects openbaoSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 2.6.3 soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade openbao to 2.6.3.

Affected software

ProductAffectedFixed in
openbaoopenbaoAffected
  • >=2.3.0 <2.6.3
Fixed in
  • 2.6.3
Goopenbaopkg:golang/openbaoOther threatsAffected
  • >=2.3.0 <2.6.3
Fixed in
  • 2.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

OpenBao from 2.3.0 before 2.6.3 contains an incorrect authorization vulnerability in its ACL policy cache that allows tokens to reference policies from arbitrary namespaces using specially crafted policy names. Attackers holding such tokens can gain capabilities of cached policies in other namespaces, including the root namespace, to act across namespace boundaries.

References

Community reviews

Loading reviews…