OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens
cve-program · CVE-2026-46405
PublishedOpenBao 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.
Read the publisher's advisoryeuvd · EUVD-2026-54683
PublishedOpenBao 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.
Read the publisher's advisorynvd · CVE-2026-46405
PublishedOpenBao 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.
Read the publisher's advisoryosv · GHSA-7j6w-vvw2-5f9c
Published### Impact 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`. At most this could cause storage usage. ### Patches This is fixed in OpenBao v2.5.4. ### Workarounds 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. ### Reporter This was discovered by an anonymous reporter.
Read the publisher's advisoryosv · GO-2026-5225
PublishedOpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens in github.com/openbao/openbao. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/openbao/openbao before v2.5.4.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-46405 · CVE overview and exploitation status
cve-program · CVE-2026-46405
- https://github.com/openbao/openbao/security/advisories/GHSA-7j6w-vvw2-5f9c
- https://github.com/openbao/openbao/pull/3150
- https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f4d
- https://github.com/openbao/openbao/releases/tag/v2.5.4
euvd · EUVD-2026-54683
- https://github.com/openbao/openbao/security/advisories/GHSA-7j6w-vvw2-5f9c
- https://github.com/openbao/openbao/pull/3150
- https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f4d
- https://github.com/openbao/openbao/releases/tag/v2.5.4
nvd · CVE-2026-46405
- https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f4d
- 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
osv · GHSA-7j6w-vvw2-5f9c
- https://github.com/openbao/openbao/security/advisories/GHSA-7j6w-vvw2-5f9c
- https://github.com/openbao/openbao/pull/3150
- https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f4d
- https://github.com/openbao/openbao
- https://github.com/openbao/openbao/releases/tag/v2.5.4