Skip to main content
Mallory
CriticalVulnerability

CVE-2026-46421: Malicious package compromise in SAP CAP SQL database service packages

Published Jul 15, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS0.52%45th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2026-46421CWE-506 · Embedded Malicious Code

CVE-2026-46421 is a software supply-chain compromise affecting SAP Cloud Application Programming Model SQL database service packages from the cap-js/cds-dbs monorepo. Malicious versions of the affected packages were published on April 29, 2026. The compromised releases of @cap-js/sqlite, @cap-js/postgres, and @cap-js/db-service contained unauthorized functionality that harvested credentials available on the host where the packages were installed and also attempted self-propagation. This is not a memory-safety or logic flaw in normal package functionality; it is a malicious code insertion event in published package versions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Installation of an affected package version can result in compromise of credentials accessible from the host environment, including development and deployment secrets such as package registry tokens, cloud provider credentials, SSH material, and source-control access tokens. The self-propagation behavior also creates risk of further downstream compromise across developer workstations, CI/CD systems, build environments, and connected repositories or infrastructure. Impact therefore includes unauthorized access, account takeover, follow-on supply-chain abuse, and broader compromise of systems reachable using stolen credentials.

Mitigation

If you can’t patch tonight, do this now.

No known workaround is available short of removing the compromised package versions and replacing them with fixed releases. Until remediation is complete, prevent use of the affected versions in dependency resolution, isolate or rebuild impacted developer and build environments as appropriate, and restrict or revoke exposed secrets to limit further abuse. Additional defensive measures include enforcing dependency pinning to trusted versions, verifying package provenance where supported, and monitoring for unauthorized use of credentials that may have been exposed.

Remediation

Patch, then assume compromise.

Upgrade to fixed package versions: @cap-js/sqlite 2.4.0 or later, @cap-js/postgres 2.3.0 or later, and @cap-js/db-service 2.11.0 or later. Any environment in which a compromised version was installed should be treated as exposed. Rotate all credentials that were present or accessible on the affected machine at the time of installation or execution, including registry tokens, cloud credentials, SSH keys, and source-control tokens. Review CI/CD secrets, revoke and reissue impacted credentials, audit repository and infrastructure access for unauthorized activity, and validate downstream artifacts produced by affected environments.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-46421 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-46421?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-46421.
Is there a patch for CVE-2026-46421?
Upgrade to fixed package versions: @cap-js/sqlite 2.4.0 or later, @cap-js/postgres 2.3.0 or later, and @cap-js/db-service 2.11.0 or later. Any environment in which a compromised version was installed should be treated as exposed.
How severe is CVE-2026-46421?
CVE-2026-46421 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.52% (45th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.