Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@cap-js/db-service

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratednpmAmendedPublished

    Supply chain compromise via malicious package versions (@cap-js/sqlite, @cap-js/postgres, @cap-js/db-service)

    CVE-2026-46421 · GHSA-pvw4-cvr4-97p8

    Affected
    • npm @cap-js/db-service >= 2.10.1, <= 2.10.1
    Fixed in
    2.11.0· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.11.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)osv.dev (2)Source checked Evidence →