Vulnerability Description
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn't possible to deny access to it.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f
- https://github.com/openbao/openbao/pull/3150
- https://github.com/openbao/openbao/releases/tag/v2.5.4
- https://github.com/openbao/openbao/security/advisories/GHSA-7j6w-vvw2-5f9c
FAQ
What is CVE-2026-46405?
CVE-2026-46405 is a vulnerability with a CVSS score of 5.3 (MEDIUM). OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supp...
How severe is CVE-2026-46405?
CVE-2026-46405 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-46405?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.