Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5pq8-3ffp-7w5m | hashi-vault-js: Vault token and secret values exposed in thrown errors |
Mon, 14 Sep 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | hashi-vault-js: Vault token and secret values exposed in thrown errors | |
| Weaknesses | CWE-209 CWE-532 |
|
| References |
|
|
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-14T17:18:55.696Z
Reserved: 2026-06-16T14:41:54.579Z
Link: CVE-2026-55102
Updated: 2026-09-14T17:18:51.810Z
Status : Received
Published: 2026-09-14T17:17:47.930
Modified: 2026-09-14T18:17:54.957
Link: CVE-2026-55102
No data.
OpenCVE Enrichment
No data.

Github GHSA