Information Disclosure in payload (CVE-2026-105861)
Summary
Vulnerability in payload (CVE-2026-105861). Confidential information can be exposed externally. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
Impact
Under certain external upload configurations, Payload could send authentication data to a destination that was not verified as trusted. If the affected request contained a valid session, this could expose that session to an unintended recipient.
You are affected if:
- You have enabled external URL-based upload retrieval, where authenticated requests can trigger it.
Patches
Payload now validates the destination before forwarding authentication data and reapplies that validation when a request changes destination.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds
It is recommended to update all Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
If you cannot, a valid workaround exists:
- Disable external URL-based upload retrieval where practical.
- If you cannot disable it, configure the upload header filter to remove authentication data from outbound file requests.
- Restrict access to the affected upload functionality.
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-105861 has been found in payload.
Confidential information can be exposed externally. CVSS score: 8.2/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-105861" on the vendor's site.
CVE-2026-105861 (payload) — CWE-200 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
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.
Information disclosure (CWE-200) exists in payload.
Check the vendor advisory for the affected versions of payload.
Severity: High (CVSS 8.2/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 '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 patch patch
Upgrade payload 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
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com