CVE-2026-46358

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
Elevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: Elevated riskExposed: 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, 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.4(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity54% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 11, 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_pr

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
generic

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

https://github.com/openbao/openbao/issues/3074
github Patch Available

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 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 / 39× 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:39 UTCEG score recompute
  11. 2026-08-23 14:27 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:58 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:33 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 00:57 UTCEG score recompute
Show 21 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 23:55 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-12 01:09 UTCEG score recompute
  5. 2026-08-11 02:22 UTCEG score recompute
  6. 2026-08-11 01:28 UTCEG score recompute
  7. 2026-08-11 00:04 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-09 19:03 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 20:17 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 20:47 UTCEG score recompute▲ 5.40
  14. 2026-08-07 20:47 UTCMITRE cvelistV5CVSS v3 → 5.4 · CVSS v4 → 5.4
  15. 2026-07-31 06:19 UTCEG score recompute
  16. 2026-07-27 09:36 UTCEG score recompute
  17. 2026-07-23 03:17 UTCEG score recompute
  18. 2026-06-14 23:18 UTCEPSS rescore
  19. 2026-06-13 23:00 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-05-28 18:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46358?
CVE-2026-46358 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, 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 CVE-2026-46358 disclosed?
CVE-2026-46358 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46358 actively exploited?
CVE-2026-46358 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 95.8% of all scored CVEs.
What is the CVSS score of CVE-2026-46358?
CVE-2026-46358 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-46358?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46358, 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-46358

Explore →

Is Your Infrastructure Affected by CVE-2026-46358?

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

Start Free Scan →Browse All CVEs