CVE-2026-55102 hashi-vault-js: Vault token and secret values exposed in thrown errors
Attackers can steal Vault tokens and secrets from application logs because the library exposes sensitive data in error objects.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-55102?
CVE-2026-55102 is a medium-severity vulnerability in kyndryl-open-source hashi-vault-js, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2026-55102?
2 open source packages ship an affected version, including hashi-vault-js.
| Package | Affected | Fixed in |
|---|---|---|
hashi-vault-js npm | All versions | 0.5.2 |
hashi-vault-js npm | All versions | 0.5.2 |
How do I fix CVE-2026-55102?
Upgrade hashi-vault-js to 0.5.2 or later.
Is CVE-2026-55102 being exploited?
There is no known exploitation of CVE-2026-55102 in the wild and no public exploit code.
Sources
Also known as GHSA-5pq8-3ffp-7w5m.