Security readout for executives and security teams
Plain-English summary
Compromised npm package versions for SAP CAP database components were published on April 29, 2026. Systems that installed them may have exposed development, cloud, source-control, and SSH credentials. Treat affected machines as credential-compromised, not just package-vulnerable.
Executive priority
Handle as an urgent supply-chain credential incident. Prioritize identifying affected installs, rotating exposed secrets, and confirming clean package versions before resuming trusted builds or deployments.
Technical view
CVE-2026-46421 covers malicious versions @cap-js/sqlite 2.2.2, @cap-js/postgres 2.2.2, and @cap-js/db-service 2.10.1 in the cap-js/cds-dbs ecosystem. The packages reportedly harvested credentials and attempted self-propagation. The issue is classified as CWE-506 with CVSS 4.0 score 9.3.
Likely exposure
Exposure is limited to environments that installed the exact compromised versions. Highest-risk locations are developer workstations, CI runners, package build hosts, and deployment systems with npm tokens, cloud credentials, SSH keys, or GitHub PATs available.
Exploitation context
The source bundle confirms malicious package publication and credential-harvesting behavior. It does not provide a KEV listing or evidence of ongoing active exploitation beyond the published compromised packages. No exploit procedure is needed to assess exposure.
Researcher notes
The evidence names exact package versions and minimum fixed versions, but does not include detailed indicators, affected installation counts, or confirmed downstream compromise scope. Focus validation on dependency resolution records, package cache history, and exposed credential inventory.
Mitigation direction
- Upgrade @cap-js/sqlite to version 2.4.0 or later.
- Upgrade @cap-js/postgres to version 2.3.0 or later.
- Upgrade @cap-js/db-service to version 2.11.0 or later.
- Rotate credentials accessible from systems that installed compromised versions.
- Check vendor guidance because sources state no known workaround.
Validation and detection
- Search package lockfiles and dependency manifests for the exact affected versions.
- Review CI, workstation, and build-host package installation logs around April 29, 2026.
- Identify secrets available to any host that installed affected packages.
- Confirm upgraded package versions are deployed across all repositories and build images.
- Verify credential rotation completion for npm, cloud, SSH, and GitHub tokens.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-506: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-46421 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/cap-js/cds-dbs/security/advisories/GHSA-pvw4-cvr4-97p8CVE reference, GitHub_M · x_refsource_CONFIRM
- https://me.sap.com/notes/3747787CVE reference, GitHub_M · x_refsource_MISC
- https://www.sap.com/documents/2026/05/8203a8b9-4d7f-0010-bca6-c68f7e60039b.htmlCVE reference, GitHub_M · x_refsource_MISC
- https://www.stepsecurity.io/blog/a-mini-shai-hulud-has-appearedCVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Embedded Malicious Code
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.