Skip to main content
VulnerabilityPublished

CVE-2026-115359: openbao · Improper Control of Interaction Frequency

Affects openbaoSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.7.1 or 2.6.4 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.1, 2.6.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/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.7.1 or 2.6.4.

Affected software

ProductAffectedFixed in
openbaoopenbaoAffected
  • >=2.7.0 <2.7.1
Fixed in
  • 2.7.1
openbaoopenbaoAffected
  • <2.6.4
Fixed in
  • 2.6.4
Goopenbaopkg:golang/openbaoOther threatsAffected
  • <2.6.4
  • >=2.7.0 <2.7.1
Fixed in
  • 2.6.4
  • 2.7.1

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

AI-suggested

A fix is available in OpenBao versions 2.6.4 and 2.7.1. Users should upgrade to these versions or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

OpenBao versions before 2.6.4 and 2.7.x before 2.7.1 have a flaw in their rate limit quota subsystem. The issue occurs because role resolution fails for requests with form-encoded bodies or forwarded certificates, causing quota rules scoped to backend-specific roles to not be enforced. This allows valid callers to repeatedly issue tokens without consuming the configured role-based rate limit budget.

References

Community reviews

Loading reviews…