CVE-2026-46405

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

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 v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-7j6w-vvw2-5f9c
github_pr

Prevent errors from creating orphaned tokens

Fix merged in openbao/openbao PR #3150 on 2026-05-20 — awaiting tagged release

https://github.com/openbao/openbao/pull/3150
github_commit

commit 0d82e0a5a3b6 (openbao/openbao)

Fix landed in openbao/openbao commit 0d82e0a5a3b6 — awaiting tagged release

https://github.com/openbao/openbao/commit/0d82e0a5a3b6a93e8087bcbaf0b11326c12d4f4d

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—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 38× 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-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:38 UTCEG score recompute
  11. 2026-08-23 14:26 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 15:24 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 10:43 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 07:45 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:32 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 14:26 UTCEG score recompute
Show 20 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 15:28 UTCEG score recompute
  3. 2026-08-13 14:26 UTCEG score recompute
  4. 2026-08-12 21:59 UTCEG score recompute
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-11 23:01 UTCEG score recompute
  7. 2026-08-11 00:03 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-09 20:29 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 21:31 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 22:33 UTCEG score recompute
  14. 2026-07-31 06:18 UTCEG score recompute
  15. 2026-07-27 09:35 UTCEG score recompute
  16. 2026-07-23 03:17 UTCEG score recompute
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-05-28 19:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46405?
CVE-2026-46405 is a medium vulnerability published on May 28, 2026. 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…
When was CVE-2026-46405 disclosed?
CVE-2026-46405 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 13, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 70.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46405?
CVE-2026-46405 has a CVSS v3 base score of 5.3 (NVD).
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