# 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.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **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:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-5pq8-3ffp-7w5m

## 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-55102?

2 open source packages ship an affected version, including hashi-vault-js.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55102 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-55102 in the wild and no public exploit code.

Affected packages and fixed versions:
- hashi-vault-js (npm): affected all versions; fixed in 0.5.2
- hashi-vault-js (npm): affected all versions; fixed in 0.5.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55102/ (Markdown: https://insights.sbomify.com/CVE-2026-55102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55102
- OSV: https://osv.dev/vulnerability/CVE-2026-55102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55102/
Summaries are generated and may contain mistakes; the official description above is the record.