Vulnerability in @cap-js/sqlite (CVE-2026-46421)
Summary
Vulnerability in @cap-js/sqlite (CVE-2026-46421). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.3.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46421 has been found in @cap-js/sqlite.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @cap-js/sqlite to 2.3.0 or later.
If unsure, ask your IT team or search "@cap-js/sqlite CVE-2026-46421" on the vendor's site.
CVE-2026-46421 (@cap-js/sqlite) — CWE-506
Patched: 2.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-506) exists in @cap-js/sqlite.
Check the vendor advisory for the affected versions of @cap-js/sqlite.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@cap-js/sqlite' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@cap-js/sqlite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@cap-js/sqliteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @cap-js/sqlite to 2.3.0ステージング環境で 2.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。