CVE-2026-45808

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: 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, OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented sys/revoke and sys/renew endpoints. This is fixed in OpenBao v2.5.4.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 13, 2026

Advisory Details (3)

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

commit c0495646b41c (openbao/openbao)

Fix landed in openbao/openbao commit c0495646b41c — awaiting tagged release

https://github.com/openbao/openbao/commit/c0495646b41cea0e3f5a1030132e9cf5c2375b5c
github_pr

Remove legacy cross-namespace lease endpoints

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

https://github.com/openbao/openbao/pull/3152
github Patch Available

Cross-namespace lease revocation via legacy sys/revoke path bypasses ACL · Advisory · openbao/openbao · GitHub

https://github.com/openbao/openbao/security/advisories/GHSA-v8v8-cm84-m686

Vendor Advisories for CVE-2026-45808(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 / 40× 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:40 UTCEG score recompute
  11. 2026-08-23 14:28 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:45 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-16 15:09 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 07:18 UTCEG score recompute
Show 22 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 19:20 UTCEG score recompute
  3. 2026-08-13 18:52 UTCEG score recompute
  4. 2026-08-12 23:55 UTCEG score recompute
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 00:00 UTCEG score recompute
  7. 2026-08-11 00:05 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-09 22:23 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-08 22:28 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 22:33 UTCEG score recompute
  14. 2026-08-07 21:22 UTCEG score recompute▲ 7.10
  15. 2026-08-07 21:22 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
  16. 2026-07-31 06:19 UTCEG score recompute
  17. 2026-07-27 09:37 UTCEG score recompute
  18. 2026-07-23 03:16 UTCEG score recompute
  19. 2026-06-14 23:18 UTCEPSS rescore
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-05-28 18:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45808?
CVE-2026-45808 is a high vulnerability published on May 28, 2026. OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the…
When was CVE-2026-45808 disclosed?
CVE-2026-45808 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-45808 actively exploited?
CVE-2026-45808 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 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-45808?
CVE-2026-45808 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-45808?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45808, 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-45808

Explore →

Is Your Infrastructure Affected by CVE-2026-45808?

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

Start Free Scan →Browse All CVEs