Vulnerability in @payloadcms/plugin-import-export (CVE-2026-105844)
Summary
Vulnerability in @payloadcms/plugin-import-export (CVE-2026-105844). 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
An unauthenticated user could cause unintended application behavior when the Import Export plugin is enabled, allowing an attacker to submit and execute remote code (RCE).
Applications that do not use @payloadcms/plugin-import-export are not affected.
Patches
Users should upgrade Payload packages to >= 3.88.0 or >= 4.0.0-canary.27.
Workarounds
Upgrading is recommended. Until then, disable the Import Export plugin or restrict access to its endpoints.
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-105844 has been found in @payloadcms/plugin-import-export.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @payloadcms/plugin-import-export to 4.0.0-canary.27 or later.
If unsure, ask your IT team or search "@payloadcms/plugin-import-export CVE-2026-105844" on the vendor's site.
CVE-2026-105844 (@payloadcms/plugin-import-export) — CWE-1321
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.
A vulnerability (CWE-1321) exists in @payloadcms/plugin-import-export.
Check the vendor advisory for the affected versions of @payloadcms/plugin-import-export.
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 '@payloadcms/plugin-import-export' . 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/plugin-import-export' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/plugin-import-exportを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrading is recommended.パッチが適用されるまでの応急処置として、Upgrading is recommended. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @payloadcms/plugin-import-export to 4.0.0-canary.27ステージング環境で 4.0.0-canary.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。