CVE-2026-55102

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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
Trending — 4 sources updated this week

Also known asEUVD-2026-77640 (ENISA EUVD) · GHSA-5pq8-3ffp-7w5m (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
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.2%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

hashi-vault-js is a Node.js module for interacting with the HashiCorp Vault API. Prior to 0.5.2, every API method in src/Vault.js passes failed requests through parseAxiosError(), which rethrows the raw AxiosError while retaining AxiosError.config and the equivalent response configuration. These objects can contain the X-Vault-Token request header and err.config.data request body, including submitted passwords or secret values. When a consuming application records the caught exception through console logging, structured loggers, monitoring, crash reporting, or an application performance monitoring service, the live Vault token and request secrets can be stored in plaintext and exposed to anyone with access to that output. A stolen token can permit unauthorized access to the Vault instance under the token's policies. This issue is fixed in version 0.5.2.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
5th
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.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 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-31). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

August 13, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Release v0.5.2

Patch available: kyndryl-open-source/hashi-vault-js v0.5.2

https://github.com/kyndryl-open-source/hashi-vault-js/releases/tag/v0.5.2
GitHub commit Patch Available

commit ed0797a2d09c (kyndryl-open-source/hashi-vault-js)

Patch available: kyndryl-open-source/hashi-vault-js v0.5.2 (contains commit ed0797a2d09c)

https://github.com/kyndryl-open-source/hashi-vault-js/commit/ed0797a2d09c1fe0fd20764dde66cbc29241d9fb
GitHub pull request Patch Available

fix/GHSA-5pq8-3ffp-7w5m

Patch available: kyndryl-open-source/hashi-vault-js v0.5.2 (PR #67 merged 2026-06-10)

https://github.com/kyndryl-open-source/hashi-vault-js/pull/67
GitHub advisoryMentions a patch (unverified)

Vault token and secret values exposed in thrown errors · Advisory · kyndryl-open-source/hashi-vault-js · GitHub

https://github.com/kyndryl-open-source/hashi-vault-js/security/advisories/GHSA-5pq8-3ffp-7w5m

Vendor Advisories for CVE-2026-55102(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmhashi-vault-js @ 0.5.2 (fixes <= 0.5.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
hashi-vault-js—
  • every version up to 0.5.2: fixed in 0.5.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-5pq8-3ffp-7w5m · GitHub severity MODERATE
  4. 2026-11-01 07:44 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-30 11:25 UTCOSV refresh
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-25 14:19 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-22 21:17 UTCEG score recompute
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-18 03:30 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 46 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:39 UTCEG score recompute
  6. 2026-10-11 16:54 UTCEG score recompute
  7. 2026-10-11 14:17 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-06 13:26 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-03 19:50 UTCEG score recompute
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-02 07:34 UTCEG score recompute
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-30 20:04 UTCEG score recompute
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-28 10:24 UTCEG score recompute
  26. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-27 09:45 UTCEG score recompute
  28. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-09-25 05:33 UTCEG score recompute
  30. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-24 04:53 UTCEG score recompute
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-09-23 04:14 UTCEG score recompute
  34. 2026-09-22 03:34 UTCEG score recompute
  35. 2026-09-19 01:23 UTCEG score recompute
  36. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-09-18 00:42 UTCEG score recompute
  38. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  39. 2026-09-17 00:02 UTCEG score recompute
  40. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-09-14 18:37 UTCEG score recompute
  43. 2026-09-14 17:55 UTCEG score recompute
  44. 2026-09-14 17:05 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  45. 2026-09-14 17:04 UTCMITRE cvelistV5CVSS v3 → 5.8 · CVSS v4 → 5.8
  46. 2026-08-13 14:52 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55102?
CVE-2026-55102 is a medium-severity vulnerability; its CVE record was published on August 13, 2026. hashi-vault-js is a Node.js module for interacting with the HashiCorp Vault API. Prior to 0.5.2, every API method in src/Vault.js passes failed requests through parseAxiosError(), which rethrows the raw AxiosError while retaining AxiosError.config and the equivalent response configuration. These…
When was the CVE record for CVE-2026-55102 published?
The CVE record for CVE-2026-55102 was published on August 13, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-55102 actively exploited?
CVE-2026-55102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55102?
CVE-2026-55102 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55102?
A fix for CVE-2026-55102 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55102 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-55102

Explore →

Is Your Infrastructure Affected by CVE-2026-55102?

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