Summary
Impact
On May 19, 2026, a compromised version of @cap-js/[email protected] was published.
The malicious packages harvested credentials and attempted self-propagation.
If a compromised version was installed, all credentials accessible on that machine (npm tokens, cloud provider credentials, SSH keys, GitHub PATs) should be considered compromised.
GHSA-JPVJ-WPMJ-H7RV has a CVSS score of 9.6 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade to @cap-js/openapi >= 1.4.2
If the compromised version was ever installed, rotate all affected credentials.
Frequently Asked Questions
- What is GHSA-JPVJ-WPMJ-H7RV? GHSA-JPVJ-WPMJ-H7RV is a critical-severity security vulnerability in @cap-js/openapi (npm), affecting versions = 1.4.1. It is fixed in 1.4.2.
- How severe is GHSA-JPVJ-WPMJ-H7RV? GHSA-JPVJ-WPMJ-H7RV has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @cap-js/openapi are affected by GHSA-JPVJ-WPMJ-H7RV? @cap-js/openapi (npm) versions = 1.4.1 is affected.
- Is there a fix for GHSA-JPVJ-WPMJ-H7RV? Yes. GHSA-JPVJ-WPMJ-H7RV is fixed in 1.4.2. Upgrade to this version or later.
- Is GHSA-JPVJ-WPMJ-H7RV exploitable, and should I be worried? Whether GHSA-JPVJ-WPMJ-H7RV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JPVJ-WPMJ-H7RV is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-JPVJ-WPMJ-H7RV? Upgrade
@cap-js/openapito 1.4.2 or later.