Quick answers
- Is CVE-2026-115356 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115356 being exploited in the wild.
- How severe is CVE-2026-115356?
- Medium severity, with a CVSS score of 5.4, published 22 October 2026.
- Which products and versions are affected?
- OpenBao before 2.6.4 and 2.7.x before 2.7.1.
- Is there a fix for CVE-2026-115356?
- Yes: fixed in OpenBao 2.6.4, 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115356 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-115356?
- Check whether you run OpenBao at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: OpenBao 2.6.4, 2.7.1
Technical details
The Kubernetes Auth method in OpenBao fails to validate that the original service account token remains valid when processing token renewal requests. An authenticated attacker with a token issued via Kubernetes Auth can exploit this to maintain access even after the backing service account is revoked, bypassing the intended access revocation mechanism. The vulnerability requires prior authentication and affects token renewal operations.
Affected products
- OpenBao OpenBao before 2.6.4 and 2.7.x before 2.7.1
Timeline
- 2026-10-01: disclosed
- 2026-10-22: advisory