Information Disclosure in payload (CVE-2026-105805)
Summary
Vulnerability in payload (CVE-2026-105805). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.0.0-canary.27 or later.
Original description
The description as published by the source.
Impact
Under certain conditions, sorting readable records could reveal limited information about fields the requester was not permitted to read.
You are affected if untrusted users can query a collection, control its sorting, and sort by protected fields.
Patches
Payload now applies field-level access checks to sort fields before executing queries.
Users should upgrade to >= 3.88.0 or >= 4.0.0-canary.27.
Workarounds
Upgrading is recommended. Until then, prevent untrusted users from controlling sort parameters or restrict their access to affected collections.
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-105805 has been found in payload.
Risk of unauthorized operations or information disclosure.
What to do: upgrade payload to 4.0.0-canary.27 or later.
If unsure, ask your IT team or search "payload CVE-2026-105805" on the vendor's site.
CVE-2026-105805 (payload) — CWE-200
Patched: 4.0.0-canary.27 — apply immediately
Workaround: Upgrading is recommended.
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: ?. Risk of unauthorized operations or information disclosure.
Update to 4.0.0-canary.27.
Workaround: Upgrading is recommended.
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
Upgrading is recommended.パッチが適用されるまでの応急処置として、Upgrading is recommended. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade payload to 4.0.0-canary.27ステージング環境で 4.0.0-canary.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com