CVE-2026-46405

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 28, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

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

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

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 rangeFix by version rangeDependents
github.com/openbao/openbao—
  • every version up to 2.5.4: fixed in 2.5.4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-18 03:37 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-12 16:02 UTCEG score recompute
  11. 2026-10-11 19:45 UTCEG score recompute
  12. 2026-10-11 17:00 UTCEG score recompute
  13. 2026-10-11 14:25 UTCEG score recompute
  14. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-03 15:18 UTCOSV refresh
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 65 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-14 06:38 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-09 23:00 UTCEG score recompute
  18. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  29. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-08-25 04:38 UTCEG score recompute
  31. 2026-08-23 14:26 UTCEG score recompute
  32. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-08-21 15:24 UTCEG score recompute
  35. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-08-20 10:43 UTCEG score recompute
  37. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-08-17 07:45 UTCEG score recompute
  41. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-08-16 02:32 UTCEG score recompute
  43. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  44. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  45. 2026-08-14 14:26 UTCEG score recompute
  46. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-13 15:28 UTCEG score recompute
  48. 2026-08-13 14:26 UTCEG score recompute
  49. 2026-08-12 21:59 UTCEG score recompute
  50. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-08-11 23:01 UTCEG score recompute
  52. 2026-08-11 00:03 UTCEG score recompute
  53. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  54. 2026-08-09 20:29 UTCEG score recompute
  55. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  56. 2026-08-08 21:31 UTCEG score recompute
  57. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  58. 2026-08-07 22:33 UTCEG score recompute
  59. 2026-07-31 06:18 UTCEG score recompute
  60. 2026-07-27 09:35 UTCEG score recompute
  61. 2026-07-23 03:17 UTCEG score recompute
  62. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 24th percentile
  63. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 24th percentile
  64. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 24th percentile
  65. 2026-05-28 19:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46405?
CVE-2026-46405 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-46405 published?
The CVE record for CVE-2026-46405 was published on May 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-46405 actively exploited?
CVE-2026-46405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46405?
CVE-2026-46405 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46405?
A fix for CVE-2026-46405 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46405 are linked in the Vendor Advisories panel on this page.

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.