SQL Injection in @payloadcms/db-sqlite (CVE-2026-105856)
Summary
SQL injection in @payloadcms/db-sqlite (CVE-2026-105856). Confidential information can be exposed externally. Exploitable via json. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
An attacker who has read plus create or update access to a collection can submit a request that includes a SQL injection targeting a specific field path shape and operators in Payload's SQLite and Postgres.
You are affected if:
- You use
@payloadcms/db-sqliteor@payloadcms/db-d1-sqlite. - You use
@payloadcms/db-postgresor@payloadcms/db-vercel-postgres< 3.73.0. - A readable collection has a
jsonfield, or ablocksfield withblocksAsJSON: true. - The attacker has read plus create or update access on it.
You are not affected if:
- You have no
json orblocksAsJSONfields.richText` is not affected. - You run a patched version.
Patches
The patched version sanitizes the query input to prevent injection.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Source: NIST National Vulnerability Database 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-105856 has been found in @payloadcms/db-sqlite.
Attackers can target a specific entry point like json over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade @payloadcms/db-sqlite to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "@payloadcms/db-sqlite CVE-2026-105856" on the vendor's site.
CVE-2026-105856 (@payloadcms/db-sqlite) — CWE-89 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: json / blocksAsJSON / richText
Patched: 4.0.0-canary.34 — 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.
SQL injection (CWE-89) exists in @payloadcms/db-sqlite. Attackers reach the vulnerable code path via json.
Check the vendor advisory for the affected versions of @payloadcms/db-sqlite. Attack surface: json / blocksAsJSON / richText.
Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.
Update to 4.0.0-canary.34.
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 '@payloadcms/db-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 '@payloadcms/db-sqlite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/db-sqliteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @payloadcms/db-sqlite to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web nvd.nist.gov
- web github.com