CVE-2026-46358

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th 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
Elevated
5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: No code on recordExposed 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, OpenBao's inline auth functionality incorrectly redacted audit log entries, resulting in non-auth headers being removed and auth-related headers being retained in cleartext. This requires an attacker to compromise access to the audit device. Operators should review leaked source authentication material and rotate it as appropriate. This is fixed in OpenBao v2.5.4.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
10th
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.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 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.2% 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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 (4)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 131c6966af4d (openbao/openbao)

Fix landed in openbao/openbao commit 131c6966af4d — awaiting tagged release

https://github.com/openbao/openbao/commit/131c6966af4dfb4e1906703436eecdb8f2a3e9df
GitHub pull request

Fix audit logs dropping custom headers when using inline auth

Fix merged in openbao/openbao PR #3076 on 2026-05-13 — awaiting tagged release

https://github.com/openbao/openbao/pull/3076
Web page

Custom headers missing from audit log when using inline auth · Issue #3074 · openbao/openbao · GitHub

https://github.com/openbao/openbao/issues/3074
GitHub advisoryMentions a patch (unverified)

OpenBao's Inline Auth Incorrectly Redacted Headers · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-q8cj-789h-vg24

Vendor Advisories for CVE-2026-46358(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 / 30× 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.2% · 10th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-18 03:37 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-12 16:03 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.2% · 10th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-03 15:18 UTCOSV refresh
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 65 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-09-14 06:39 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  16. 2026-09-09 23:00 UTCEG score recompute
  17. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  28. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  29. 2026-08-25 04:39 UTCEG score recompute
  30. 2026-08-23 14:27 UTCEG score recompute
  31. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  32. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  33. 2026-08-21 15:24 UTCEG score recompute
  34. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  35. 2026-08-20 10:43 UTCEG score recompute
  36. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  37. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  38. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  39. 2026-08-17 07:58 UTCEG score recompute
  40. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  41. 2026-08-16 02:33 UTCEG score recompute
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  44. 2026-08-14 00:57 UTCEG score recompute
  45. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  46. 2026-08-12 23:55 UTCEG score recompute
  47. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  48. 2026-08-12 01:09 UTCEG score recompute
  49. 2026-08-11 02:22 UTCEG score recompute
  50. 2026-08-11 01:28 UTCEG score recompute
  51. 2026-08-11 00:04 UTCEG score recompute
  52. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-09 19:03 UTCEG score recompute
  54. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-08-08 20:17 UTCEG score recompute
  56. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  57. 2026-08-07 20:47 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  58. 2026-08-07 20:47 UTCMITRE cvelistV5CVSS v3 → 5.4 · CVSS v4 → 5.4
  59. 2026-07-31 06:19 UTCEG score recompute
  60. 2026-07-27 09:36 UTCEG score recompute
  61. 2026-07-23 03:17 UTCEG score recompute
  62. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  63. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  64. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  65. 2026-05-28 18:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46358?
CVE-2026-46358 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, OpenBao's inline auth functionality incorrectly redacted audit log entries, resulting in non-auth headers being removed and auth-related headers being retained in cleartext. This requires an attacker to…
When was the CVE record for CVE-2026-46358 published?
The CVE record for CVE-2026-46358 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-46358 actively exploited?
CVE-2026-46358 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46358?
CVE-2026-46358 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46358?
A fix for CVE-2026-46358 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46358 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-46358

Explore →

Is Your Infrastructure Affected by CVE-2026-46358?

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