CVE-2026-46421
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe SAP Cloud Application Programming Model is a tool for building enterprise-grade cloud applications, and cap-js/cds-dbs is the monorepo for SQL database services for that tool. 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. User should 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. No known workarounds are available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a supply chain attack where malicious versions of SAP's Cloud Application Programming Model database packages (@cap-js/[email protected], @cap-js/[email protected], @cap-js/[email protected]) were published to npm. The compromised packages harvest credentials (npm tokens, cloud provider credentials, SSH keys, GitHub PATs) from the local machine and attempt self-propagation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check @cap-js/sqlite versionRun 'npm list @cap-js/sqlite' or inspect package.json dependenciesAffected if Version is exactly 2.2.2 (compromised) or falls between 2.2.2 and 2.4.0 (if other malicious variants existed)
-
Check @cap-js/postgres versionRun 'npm list @cap-js/postgres' or inspect package.json dependenciesAffected if Version is exactly 2.2.2 (compromised) or falls between 2.2.2 and 2.3.0 (if other malicious variants existed)
-
Check @cap-js/db-service versionRun 'npm list @cap-js/db-service' or inspect package.json dependenciesAffected if Version is exactly 2.10.1 (compromised) or falls between 2.10.1 and 2.11.0 (if other malicious variants existed)
-
Review package-lock.json for malicious versionsSearch package-lock.json for '"@cap-js/sqlite": "2.2.2"', '"@cap-js/postgres": "2.2.2"', or '"@cap-js/db-service": "2.10.1"'Affected if Any of these exact version strings appear in package-lock.json
If any of the three packages are installed at versions 2.2.2 (sqlite/postgres) or 2.10.1 (db-service), the environment is compromised and credentials should be considered exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately upgrade to @cap-js/sqlite >= 2.4.0, @cap-js/postgres >= 2.3.0, and @cap-js/db-service >= 2.11.0. If any compromised version was installed, treat all credentials on that machine as compromised and rotate them immediately.
@cap-js/sqlite >= 2.4.0, @cap-js/postgres >= 2.3.0, @cap-js/db-service >= 2.11.0
- Check package.json to identify which of these packages are installed: @cap-js/sqlite, @cap-js/postgres, or @cap-js/db-service
- For each affected package, run: npm install @cap-js/sqlite@^2.4.0 (or the appropriate version)
- Run npm install to update lockfile and reinstall dependencies
- After upgrading, immediately rotate ALL credentials that were present on the machine where the compromised package was installed, including: npm tokens, cloud provider credentials (AWS/Azure/GCP), SSH keys, and GitHub personal access tokens (PATs)
- Review npm audit logs and CI/CD pipelines for any suspicious activity
- Consider rotating credentials even if no obvious malicious activity was observed, as the package had self-propagation capability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46421 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data