CVE-2026-55100: Hashi vault js Path Traversal Vulnerability
HIGHCVE-2026-55100 is a HIGH path traversal vulnerability (CWE-23: Relative Path Traversal) affecting Hashi vault js libraries in the npm ecosystem. The issue involves hashi-vault-js has a path traversal and query parameter injection. Remediation is available by upgrading affected packages to version 0.5.2.
CVE-2026-55100 at a Glance
How to Fix CVE-2026-55100
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-55100, 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-23: Relative Path Traversal, where the product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. 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-55100 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-55100?
Which Hashi vault js versions are affected?
What version fixes CVE-2026-55100?
Is hashi-vault-js affected?
What CWE is associated with CVE-2026-55100?
How can I check npm dependencies for CVE-2026-55100?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g956-2f74-rmv7",
"modified" : "2026-07-31T17:03:27Z",
"published" : "2026-07-31T17:03:27Z",
"aliases" : [ "CVE-2026-55100" ],
"summary" : "hashi-vault-js has a path traversal and query parameter injection",
"details" : "## Summary\n\nThe `hashi-vault-js` library is vulnerable to path traversal and query string injection due to the lack of proper encoding of identifiers in path segments and query strings. This allows attackers to manipulate the request URL and potentially access unintended downstream endpoints or inject malicious parameters if untrusted input is passed to the library.\n\n## Details\n\nThere are zero calls to `encodeURIComponent` anywhere in `Vault.js`. Every identifier (e.g., name, username, group, role, version) provided to the library is concatenated straight into the HTTP URL without URI encoding.\n\nTwo vectors can be dynamically confirmed:\n\n1. **Path Traversal:** Passing `../../sys/seal` as a secret name causes the HTTP client to normalize the path and send the request to `/v1/sys/seal` instead of the intended Key-Value path.\n2. **Query Injection:** Passing `1&list=true` as a version value injects an extra query parameter into the request payload.\n\n## Impact\n\nIn applications where Vault identifiers originate from untrusted user input, this allows an unauthenticated attacker to redirect requests to unintended Vault endpoints (including administrative paths under `sys/`) or otherwise alter the executed query, executing operations within the permissions of the Vault token used by the application.\n\n## Patches\n\nThis vulnerability has been addressed by wrapping path segments with `encodeURIComponent()` and safely formatting query strings instead of manual string concatenation. Users should upgrade to a version that includes this fix.\n\n## Workarounds\n\nIf you cannot immediately update the library, you can mitigate this issue by rigidly validating and sanitizing all user-supplied input before passing it into `hashi-vault-js` methods. Alternatively, manually encode inputs using `encodeURIComponent()` before supply them to the library's functions.\n\n## Acknowledgements\n\nhashi-vault-js would like to thank Sebastián Alba Vives for reporting this vulnerability.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"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-g956-2f74-rmv7"
}, {
"type" : "WEB",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js/pull/66"
}, {
"type" : "WEB",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js/commit/ea2f76052d366a08f35f62ef4c12b6a334c91ec2"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js"
}, {
"type" : "WEB",
"url" : "https://github.com/kyndryl-open-source/hashi-vault-js/releases/tag/v0.5.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-23", "CWE-74" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-31T17:03:27Z",
"nvd_published_at" : null
}
}