GHSA-jpvj-wpmj-h7rv Supply chain compromise via malicious @cap-js/openapi

Not scored Published

A compromised npm package harvested credentials and self-propagated, requiring immediate upgrade and credential rotation for affected users.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is GHSA-jpvj-wpmj-h7rv?

GHSA-jpvj-wpmj-h7rv is a vulnerability in @cap-js/openapi, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Patches

Upgrade to @cap-js/openapi >= 1.4.2 If the compromised version was ever installed, rotate all affected credentials.

Workarounds

No workarounds.

References

Which versions are affected by GHSA-jpvj-wpmj-h7rv?

2 open source packages ship an affected version, including @cap-js/openapi.

PackageAffectedFixed in
@cap-js/openapi npmFrom 1.4.11.4.2
@cap-js/openapi npmFrom 1.4.11.4.2

How do I fix GHSA-jpvj-wpmj-h7rv?

Upgrade @cap-js/openapi to 1.4.2 or later.

Is GHSA-jpvj-wpmj-h7rv being exploited?

There is no known exploitation of GHSA-jpvj-wpmj-h7rv in the wild and no public exploit code.

Sources

Is GHSA-jpvj-wpmj-h7rv in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free