Vulnerabilities in pkg:npm/hashi-vault-js
PACKAGECVE-2026-55102 is a MODERATE vault token and secret values vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting hashi-vault-js libraries in the npm ecosystem. The issue involves vault token and secret values exposed in thrown errors. Remediation is available by upgrading affected packages to version 0.5.2.
pkg:npm/hashi-vault-js
Vulnerability advisories affecting package pkg:npm/hashi-vault-js. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-5pq8-3ffp-7w5m | CVE-2026-55102 | MODERATE | hashi-vault-js: Vault token and secret values exposed in thrown errors |
| GHSA-g956-2f74-rmv7 | CVE-2026-55100 | HIGH | hashi-vault-js has a path traversal and query parameter injection |
CVE-2026-55102 at a Glance
How to Fix CVE-2026-55102
To remediate this vulnerability, upgrade all affected hashi-vault-js dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install hashi-vault-js@0.5.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls hashi-vault-js
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-55102, inspect your project dependencies using npm:
npm ls hashi-vault-js
Analyze the terminal output to locate any version of hashi-vault-js in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.2), your application is affected.
Note: The npm ls hashi-vault-js command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In hashi-vault-js, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55102 Affected hashi-vault-js Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
hashi-vault-js
|
npm |
< 0.5.2
|
0.5.2
|
References
Frequently Asked Questions
What is CVE-2026-55102?
Which hashi-vault-js versions are affected?
What version fixes CVE-2026-55102?
Is hashi-vault-js affected?
What CWE is associated with CVE-2026-55102?
How can I check npm dependencies for CVE-2026-55102?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5pq8-3ffp-7w5m",
"modified" : "2026-08-13T14:14:32Z",
"published" : "2026-08-13T14:14:32Z",
"aliases" : [ "CVE-2026-55102" ],
"summary" : "hashi-vault-js: Vault token and secret values exposed in thrown errors",
"details" : "## Summary\n\nVault token and secret values are exposed in thrown errors when using `hashi-vault-js`.\n\n## Details\n\nEvery API method in `Vault.js` executes `throw parseAxiosError(err)`, which returns the raw `AxiosError` untouched. That error carries the full Axios configuration, including the `X-Vault-Token` header and the request body. Consuming applications that log caught errors (e.g., using `console.error`, `pino`, `winston`, Sentry, or APMs) inadvertently log the live Vault token in plaintext. Furthermore, write-path methods expose submitted passwords and secret values via `err.config.data`.\n\n## Impact\n\nWhen consuming applications log intercepted exceptions, sensitive credentials such as tokens, passwords, and secrets are unknowingly exposed to application logs, monitoring services, and APM systems via the raw `AxiosError`. This may lead to authorization bypass or unauthorized access to the underlying Vault instance.\n\n## Patches\n\nThis vulnerability should be addressed by redacting `err.config.headers['X-Vault-Token']` and `err.config.data` before re-throwing, or by throwing a purpose-built error containing only safe properties like status and message. Users should upgrade to a version that includes this fix.\n\n## Workarounds\n\nIf users cannot immediately update the library, they can mitigate this issue by capturing all exceptions thrown by `hashi-vault-js` and sanitizing or omitting the `err.config` object before passing the errors to logging utilities or crash reporters.\n\n## Acknowledgements\nhashi-vault-js would like to thank Sebastián Alba Vives for reporting this vulnerability.\n\n## Resources\n\n- [CWE-532: Insertion of Sensitive Information into Log File](https://cwe.mitre.org/data/definitions/532.html)\n- [CWE-209: Generation of Error Message Containing Sensitive Information](https://cwe.mitre.org/data/definitions/209.html)",
"severity" : [ ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "hashi-vault-js"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.5.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.5.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js/security/advisories/GHSA-5pq8-3ffp-7w5m"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-209", "CWE-532" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-13T14:14:32Z",
"nvd_published_at" : null
}
}