Read the docs

OpenBao Kubernetes Auth Token Renewal Keeps Access After Account Deletion

Priority LOW 23CWE-613Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-613.

Summary

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.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00213 11th percentileScored 2026-11-07
Fix Fixed openbao (openbao): 2.6.4, 2.7.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openbaoopenbaobefore 2.6.4; 2.7.0 to before 2.7.12.6.4, 2.7.1Patch availableCNA
  • openbao Vendoropenbao Affected before 2.6.4; 2.7.0 to before 2.7.1 Fixed in 2.6.4, 2.7.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:*——openbao
  • cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:* Versions — — ·openbao

Remediation

Upgrade OpenBao to version 2.6.4 or 2.7.1, which fix the issue. The CVSS 4.0 score is 5.3 (MEDIUM), and CWE-613 (Insufficient Session Expiration) is the associated weakness.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

  • Fix · CNA openbao (openbao) Fixed in 2.6.4, 2.7.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    openbao 2.6.4, 2.7.1

    5 records Highest priority Priority LOW 5 LOW

    Other records, highest priority first

    • TI-2026-79446 OpenBao Role-Based Rate Limit Quota Bypass via Request ParsingPriority LOW 27
    • TI-2026-79449 OpenBao AppRole accepts expired Secret IDs until periodic tidyPriority LOW 11
    • TI-2026-79444 OpenBao drops response audit logs for root generation and rekeyPriority LOW 11

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-22 Threatist record created from CVE-2026-115356
  2. 2026-10-22 Alias added: GHSA-qmv6-f44g-mj35
  3. 2026-10-23 CISA SSVC decision points changed
  4. 2026-11-03 Affected versions changed · Red Hat
  5. 2026-11-03 CVSS score added · Red Hat

References

  • TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
  • TI-2026-34075 OpenBao's Inline Auth Incorrectly Redacted Headers CVSS 4.0MEDIUM 5.4
  • TI-2026-40259 OpenBao: LDAPi ldaputil (wrong escape func) CVSS 3.1MEDIUM 6.8
  • TI-2026-40265 OpenBao: Transit secrets engine crashes on key creation with `derived: true` for asymmetric key types CVSS 3.1MEDIUM 6.5
  • TI-2026-28381 OpenBao has Decompression Bomb via Unbounded Copy in OCI Plugin Extraction (DoS) CVSS 3.1MEDIUM 6.5
  • TI-2026-45068 OpenBao's Recovery Mode Vulnerable To Token Leakage via Timing Attack CVSS 4.0CRITICAL 9.2
See all 48 →

Sources