GHSA-PVW4-CVR4-97P8

Vulnerability from github – Published: 2026-05-20 15:33 – Updated: 2026-05-20 15:33
VLAI
Summary
Supply chain compromise via malicious package versions (@cap-js/sqlite, @cap-js/postgres, @cap-js/db-service)
Details

Impact

On April 29, 2026, compromised versions of @cap-js/sqlite@2.2.2, @cap-js/postgres@2.2.2, and @cap-js/db-service@2.10.1 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.

Patches

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.

Workarounds

No workarounds.

Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@cap-js/sqlite"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.2.2"
            },
            {
              "fixed": "2.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.2.2"
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@cap-js/postgres"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.2.2"
            },
            {
              "fixed": "2.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.2.2"
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@cap-js/db-service"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.10.1"
            },
            {
              "fixed": "2.11.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.10.1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-46421"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-506"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-20T15:33:04Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "## Impact\n\nOn April 29, 2026, compromised versions of `@cap-js/sqlite@2.2.2`, `@cap-js/postgres@2.2.2`, and `@cap-js/db-service@2.10.1` were published.\nThe malicious packages harvested credentials and attempted self-propagation.\nIf a compromised version was installed, all credentials accessible on that machine (npm tokens, cloud provider credentials, SSH keys, GitHub PATs) should be considered compromised.\n\n## Patches\n\nUpgrade to `@cap-js/sqlite` \u003e= 2.4.0, `@cap-js/postgres` \u003e= 2.3.0, `@cap-js/db-service` \u003e= 2.11.0.\nIf a compromised version was ever installed, rotate all affected credentials.\n\n## Workarounds\n\nNo workarounds.",
  "id": "GHSA-pvw4-cvr4-97p8",
  "modified": "2026-05-20T15:33:04Z",
  "published": "2026-05-20T15:33:04Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/cap-js/cds-dbs/security/advisories/GHSA-pvw4-cvr4-97p8"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/cap-js/cds-dbs"
    },
    {
      "type": "WEB",
      "url": "https://me.sap.com/notes/3747787"
    },
    {
      "type": "WEB",
      "url": "https://www.sap.com/documents/2026/05/8203a8b9-4d7f-0010-bca6-c68f7e60039b.html"
    },
    {
      "type": "WEB",
      "url": "https://www.stepsecurity.io/blog/a-mini-shai-hulud-has-appeared"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": " Supply chain compromise via malicious package versions (@cap-js/sqlite,  @cap-js/postgres, @cap-js/db-service)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.