Path Traversal in payload (CVE-2026-105865)
Summary
Path traversal in payload (CVE-2026-105865). Data can be tampered with by attackers. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
Under certain conditions, an authenticated user with permission to modify uploads could cause unintended files to be removed during file cleanup. This may result in data loss or service disruption.
You are affected if:
- You use Payload upload collections with local file storage.
- Untrusted authenticated users can update or delete uploads.
Deployments that restrict upload management to trusted users are less exposed.
Patches
Payload now validates uploaded filenames and ensures file cleanup remains within the configured upload directory.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
Restrict upload update and deletion operations to trusted users and validate submitted filenames. These measures are temporary mitigations. Upgrading to a patched version 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-105865 has been found in payload.
Data can be tampered with by attackers. 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-105865" on the vendor's site.
CVE-2026-105865 (payload) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Restrict upload update and deletion operations to trusted users and validate submitted filenames.
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.
Path traversal (CWE-22) exists in payload.
Check the vendor advisory for the affected versions of payload.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 4.0.0-canary.34.
Workaround: Restrict upload update and deletion operations to trusted users and validate submitted filenames.
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
Restrict upload update and deletion operations to trusted users and validate submitted filenames.パッチが適用されるまでの応急処置として、Restrict upload update and deletion operations to trusted users and validate submitted filenames. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com