Vulnerability in payload (CVE-2026-105851)
Summary
Vulnerability in payload (CVE-2026-105851). Confidential information can be exposed externally. Exploitable via access.read. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
Payload's duplicate operation copies field values from the source document even when a field is hidden, or its access.read or access.create rule would reject the value for that caller.
The disableDuplicate collection setting, enabled by default on auth collections, did not stop this.
Patches
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
Add a beforeDuplicate field hook to fields and set the value to empty or your default value.
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-105851 has been found in payload.
Attackers can target a specific entry point like access.read over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade payload to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "payload CVE-2026-105851" on the vendor's site.
CVE-2026-105851 (payload) — CWE-284 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: access.read / access.create / disableDuplicate
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Add a beforeDuplicate field hook to fields and set the value to empty or your default value.
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-284) exists in payload. Attackers reach the vulnerable code path via access.read.
Check the vendor advisory for the affected versions of payload. Attack surface: access.read / access.create / disableDuplicate.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 4.0.0-canary.34.
Workaround: Add a beforeDuplicate field hook to fields and set the value to empty or your default value.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'payload' . 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 'payload' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
payloadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Add a beforeDuplicate field hook to fields and set the value to empty or your default value.パッチが適用されるまでの応急処置として、Add a beforeDuplicate field hook to fields and set the value to empty or your default value. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade payload to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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 github.com