CVE-2026-39388

LOWNVD 3.13.1
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 3.1 under NVD CVSS v3. EPSS exploit probability: 0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-24029 (ENISA EUVD) · GO-2026-5213 (OSV.dev)Source: ENISA EUVD

3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.1Exploit: 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.3, OpenBao's Certificate authentication method, when a token renewal is requested and disable_binding=true is set, attempts to verify the current request's presented mTLS certificate matches the original. Token renewals for other authentication methods do not require any supplied login information. Due to incorrect matching, the certificate authentication method would allow renewal of tokens for which the attacker had a sibling certificate+key signed by the same CA, but which did not necessarily match the original role or the originally supplied certificate. This implies an attacker could still authenticate to OpenBao in a similar scope, however, token renewal implies that an attacker may be able to extend the lifetime of dynamic leases held by the original token. This attack requires knowledge of either the original token or its accessor. This vulnerability is original from HashiCorp Vault. This is addressed in v2.5.3. As a workaround, ensure privileged roles are tightly scoped to single certificates.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/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)
Severity31% × 45%
Impact severity (EG Severity): CVSS 3.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
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 (3.1): severity, escalated by confirmed exploitation. This CVE's 3.1 is its impact severity (EG Severity), not escalated.

EG Severity
3.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

April 21, 2026

Last Modified

April 24, 2026

References (1)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/openbao/openbao—
  • every version up to 0.0.0-20260420160924-abe84e1af4c3: fixed in 0.0.0-20260420160924-abe84e1af4c3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 36× 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.

Showing the most recent 96 of 168 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-39388?
CVE-2026-39388 is a low-severity vulnerability; its CVE record was published on April 21, 2026. OpenBao is an open source identity-based secrets management system. Prior to version 2.5.3, OpenBao's Certificate authentication method, when a token renewal is requested and disable_binding=true is set, attempts to verify the current request's presented mTLS certificate matches the original. Token…
When was the CVE record for CVE-2026-39388 published?
The CVE record for CVE-2026-39388 was published on April 21, 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 April 24, 2026; the record at its source may have been updated since.
Is CVE-2026-39388 actively exploited?
CVE-2026-39388 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39388?
CVE-2026-39388 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-39388?
A fix for CVE-2026-39388 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39388

Explore →

Is Your Infrastructure Affected by CVE-2026-39388?

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

Book a Demo →Browse All CVEs