Vulnerability in @payloadcms/storage-s3 (CVE-2026-105867)
Summary
Vulnerability in @payloadcms/storage-s3 (CVE-2026-105867). Data can be tampered with by attackers. Exploitable via false. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation.
You are affected if ALL of these are true:
- Client uploads are enabled for multiple collections that share an S3 bucket.
- useCompositePrefixes is not configured or is set to
false.
Patches
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
Disable client uploads until you can upgrade.
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-105867 has been found in @payloadcms/storage-s3.
Attackers can target a specific entry point like false over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @payloadcms/storage-s3 to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "@payloadcms/storage-s3 CVE-2026-105867" on the vendor's site.
CVE-2026-105867 (@payloadcms/storage-s3) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: false
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Disable client uploads until you can upgrade.
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/storage-s3. Attackers reach the vulnerable code path via false.
Check the vendor advisory for the affected versions of @payloadcms/storage-s3. Attack surface: false.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 4.0.0-canary.34.
Workaround: Disable client uploads until you can upgrade.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@payloadcms/storage-s3' . 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/storage-s3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/storage-s3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable client uploads until you can upgrade.パッチが適用されるまでの応急処置として、Disable client uploads until you can upgrade. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @payloadcms/storage-s3 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
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com