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.
CVE-2026-55102
This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.8
- EG Score
- 5.8MEDIUMmedium confidence
- EG Risk
- 26EG Risk 26/100CISA SSVC
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 computedSeverity58% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 4th
- KEV
- Not listed
CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 13, 2026
Last Modified
September 30, 2026
Advisory Details (4)
Auto-updated Sep 14, 2026Release 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.2commit 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/ed0797a2d09c1fe0fd20764dde66cbc29241d9fbfix/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/67Vault 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-7w5mVendor 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.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| hashi-vault-js | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 31× 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.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 19:50 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 07:34 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 20:04 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-28 10:24 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 09:45 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 05:33 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 04:53 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 04:14 UTCEG score recompute
- 2026-09-22 03:34 UTCEG score recompute
- 2026-09-19 01:23 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 00:42 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 00:02 UTCEG score recompute
Show 7 moreShow fewer
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 18:37 UTCEG score recompute
- 2026-09-14 17:55 UTCEG score recompute
- 2026-09-14 17:05 UTCEG score recompute▲ 5.80
- 2026-09-14 17:04 UTCMITRE cvelistV5CVSS v3 → 5.8 · CVSS v4 → 5.8
- 2026-08-13 14:52 UTCEG score recompute
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-55102?
When was CVE-2026-55102 disclosed?
Is CVE-2026-55102 actively exploited?
What is the CVSS score of CVE-2026-55102?
How do I remediate CVE-2026-55102?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55102
Is Your Infrastructure Affected by CVE-2026-55102?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.