Medium 5.4Published Oct 22, 2026

CVE-2026-115356OpenBao before 2.6.4 and 2.7.0 before 2.7.1 Kubernetes Auth Method Token Renewal After Revocation

Updated under an hour ago (Oct 27, 2026, 4:30 PM ET)

Does this affect you?

It affects openbao. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for openbao

Exploited in the last 30 days

OpenBao before 2.6.4 and 2.7.x before 2.7.1 does not verify, when renewing a token issued by the Kubernetes Auth method, that the service account token originally used to authenticate is still valid. An authenticated attacker can keep renewing such tokens to persist access after the Kubernetes service account has been deleted.

CVSS: 5.4 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Weakness (CWE): CWE-613
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Deferred
Record last updated: Oct 23, 2026
First seen by InfoSec Signals: Oct 22, 2026

Affected products

Affected products

openbao openbao openbao:openbao (from the name)	before 2.6.4; 2.6.4 not affected; from 2.7.0 before 2.7.1; 2.7.1 not affected	CNA record

References

References

https://github.com/openbao/openbao/security/advisories/GHSA-gf3j-hm38-jhh5	vendor-advisory
https://www.vulncheck.com/advisories/openbao-before-2.6.4-and-2.7.0-before-2.7.1-kubernetes-auth-method-token-renewal-after-revocation	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.