Malicious package compromise in SAP CAP SQL database service packages
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
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.
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.
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.
No public exploits tracked yet. Mallory keeps watching.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.