Medium [CVE-2026-46405] Denial of Service from unaccessible token accumulation in Kerberos authentication.
This medium-severity Red Hat Linux advisory covers CVE-2026-46405.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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.
When the Kerberos authentication method processes a `GET` request or an `Authorization: Negotiate` header, it inadvertently creates authentication tokens that are not accessible to the caller and are hidden by an error message. These unaccessible tokens accumulate, potentially leading to a denial of service (DoS) by consuming system resources.
A remote, unauthenticated attacker could trigger this condition. Red Hat products do not ship the OpenBao server.
- < 2.5.4
Official advisory · high-confidence parse· fetched 29 days ago·verify at source
Mitigation checklist
- Update OpenBao to version 2.5.4 or later, which limits Kerberos authentication token accumulation.
Official advisory · high-confidence parse· fetched 29 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.