Vulnerability in @payloadcms/db-mongodb (CVE-2026-106100)
Summary
Vulnerability in @payloadcms/db-mongodb (CVE-2026-106100). Data can be tampered with by attackers. Mitigation: upgrade to 4.0.0-canary.20 or later.
Original description
The description as published by the source.
Impact
A vulnerability in field-level access control could allow an authenticated user to modify fields they are not permitted to change on documents they can otherwise update.
You are affected if:
Payload version < 3.87.0 (or a 4.0.0-canary release before 4.0.0-canary.20) using the MongoDB adapter (@payloadcms/db-mongodb) with any collection that relies on field-level access control to restrict writes under certain conditions.
Relational adapters (Postgres, SQLite) are not affected.
Patches
Handling of incoming field data has been hardened so field-level access control is enforced consistently.
Users should upgrade to 3.87.0 (or 4.0.0-canary.20 on the 4.x line) or later.
Workarounds
There is no complete workaround. Upgrading to 3.87.0 (or 4.0.0-canary.20 on the 4.x line) is recommended.
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-106100 has been found in @payloadcms/db-mongodb.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @payloadcms/db-mongodb to 4.0.0-canary.20 or later.
If unsure, ask your IT team or search "@payloadcms/db-mongodb CVE-2026-106100" on the vendor's site.
CVE-2026-106100 (@payloadcms/db-mongodb) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.0-canary.20 — apply immediately
Workaround: There is no complete workaround.
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-639) exists in @payloadcms/db-mongodb.
Check the vendor advisory for the affected versions of @payloadcms/db-mongodb.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 4.0.0-canary.20.
Workaround: There is no complete workaround.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@payloadcms/db-mongodb' . 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-mongodb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/db-mongodbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no complete workaround.パッチが適用されるまでの応急処置として、There is no complete workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @payloadcms/db-mongodb to 4.0.0-canary.20ステージング環境で 4.0.0-canary.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com