CVE-2026-46405

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens

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.

CVSS v3
5.3
EG Score
5.3(low)
EPSS
24.5%
KEV
Not listed

Published

May 28, 2026

Last Modified

May 28, 2026

Vendor Advisories for CVE-2026-46405(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/openbao/openbao—2.5.4—

Data Freshness Timeline

(refreshed 2× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 02:43 UTCEG score recompute
  2. 2026-07-11 19:36 UTCEG score recompute
  3. 2026-07-08 17:58 UTCEG score recompute
  4. 2026-07-02 10:23 UTCEG score recompute
  5. 2026-07-01 02:39 UTCEG score recompute
  6. 2026-06-29 15:52 UTCEG score recompute
  7. 2026-06-28 16:23 UTCEG score recompute
  8. 2026-06-27 15:42 UTCEG score recompute
  9. 2026-06-26 16:42 UTCEG score recompute
  10. 2026-06-25 15:22 UTCEG score recompute
  11. 2026-06-24 16:22 UTCEG score recompute
  12. 2026-06-18 23:53 UTCEG score recompute
  13. 2026-06-17 10:48 UTCEG score recompute
  14. 2026-06-16 11:48 UTCEG score recompute
  15. 2026-06-15 12:49 UTCEG score recompute
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-14 13:01 UTCEG score recompute
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-13 14:03 UTCEG score recompute
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 15:04 UTCEG score recompute
  22. 2026-06-11 16:06 UTCEG score recompute
  23. 2026-06-10 16:35 UTCEG score recompute
  24. 2026-06-09 17:37 UTCEG score recompute
  25. 2026-06-08 18:38 UTCEG score recompute
Show 9 more
  1. 2026-06-07 17:49 UTCEG score recompute
  2. 2026-06-06 18:51 UTCEG score recompute
  3. 2026-06-05 19:53 UTCEG score recompute
  4. 2026-06-04 20:55 UTCEG score recompute
  5. 2026-06-03 21:57 UTCEG score recompute
  6. 2026-06-02 22:59 UTCEG score recompute
  7. 2026-06-02 00:01 UTCEG score recompute
  8. 2026-06-01 01:02 UTCEG score recompute
  9. 2026-05-28 19:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46405?
CVE-2026-46405 is a medium vulnerability published on May 28, 2026. OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens 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…
When was CVE-2026-46405 disclosed?
CVE-2026-46405 was first published in the National Vulnerability Database on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46405 actively exploited?
CVE-2026-46405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46405?
CVE-2026-46405 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-46405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46405, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46405

Explore →

Is Your Infrastructure Affected by CVE-2026-46405?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs