What is CVE-2026-46421?

CVE-2026-46421 is a critical-severity security vulnerability in @cap-js/sqlite (npm), affecting versions = 2.2.2. It is fixed in 2.3.0, 2.11.0.

Which packages are affected by CVE-2026-46421?

@cap-js/sqlite (npm) versions = 2.2.2; @cap-js/postgres (npm) versions = 2.2.2; @cap-js/db-service (npm) versions = 2.10.1.

Is there a fix for CVE-2026-46421?

Yes. CVE-2026-46421 is fixed in 2.3.0, 2.11.0. Upgrade to this version or later.

Is CVE-2026-46421 exploitable, and should I be worried?

Whether CVE-2026-46421 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.

What actually determines whether CVE-2026-46421 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 CVE-2026-46421?

Upgrade: @cap-js/sqlite to 2.3.0 or later, @cap-js/postgres to 2.3.0 or later, @cap-js/db-service to 2.11.0 or later.

CVE-2026-46421 in @cap-js/sqlite

Summary

Supply chain compromise via malicious package versions (@cap-js/sqlite, @cap-js/postgres, @cap-js/db-service)

Workarounds

No workarounds.

Impact

On April 29, 2026, compromised versions of @cap-js/[email protected], @cap-js/[email protected], and @cap-js/[email protected] were 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.

Affected versions

@cap-js/sqlite (= 2.2.2) @cap-js/postgres (= 2.2.2) @cap-js/db-service (= 2.10.1)

Security releases

@cap-js/sqlite → 2.3.0 (npm) @cap-js/postgres → 2.3.0 (npm) @cap-js/db-service → 2.11.0 (npm)

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.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade to @cap-js/sqlite >= 2.4.0, @cap-js/postgres >= 2.3.0, @cap-js/db-service >= 2.11.0.
If a compromised version was ever installed, rotate all affected credentials.

Frequently Asked Questions

What is CVE-2026-46421? CVE-2026-46421 is a critical-severity security vulnerability in @cap-js/sqlite (npm), affecting versions = 2.2.2. It is fixed in 2.3.0, 2.11.0.
Which packages are affected by CVE-2026-46421?
- @cap-js/sqlite (npm) (versions = 2.2.2)
- @cap-js/postgres (npm) (versions = 2.2.2)
- @cap-js/db-service (npm) (versions = 2.10.1)
Is there a fix for CVE-2026-46421? Yes. CVE-2026-46421 is fixed in 2.3.0, 2.11.0. Upgrade to this version or later.
Is CVE-2026-46421 exploitable, and should I be worried? Whether CVE-2026-46421 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 CVE-2026-46421 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 CVE-2026-46421?
- Upgrade @cap-js/sqlite to 2.3.0 or later
- Upgrade @cap-js/postgres to 2.3.0 or later
- Upgrade @cap-js/db-service to 2.11.0 or later