CVE-2026-105844: Payload: Prototype pollution in Payload Import Export plugin

Published Oct 6, 2026
·
Updated

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.

Other sources

Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.88.0 and canary versions before 4.0.0-canary.27, an unauthenticated user can submit prototype-sensitive field paths when @payloadcms/plugin-import-export is enabled, causing unintended application behavior that can lead to remote code execution. This issue is fixed in versions 3.88.0 and 4.0.0-canary.27.

— MITRE

Affected Software

3 affected componentsFixes available
Payload Payload>=3.0.0<3.88.0, <4.0.0-canary.27
npm/@payloadcms/plugin-import-export>=4.0.0-canary.0<4.0.0-canary.27
4.0.0-canary.27
npm/@payloadcms/plugin-import-export>=3.0.0<3.88.0
3.88.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@payloadcms/plugin-import-export to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.27
  2. Upgrade

    Upgrade npm/@payloadcms/plugin-import-export to a version that resolves this vulnerability.

    Fixed in 3.88.0
  3. Upgrade

    Upgrade Payload to a version that resolves this vulnerability.

    Fixed in 3.88.0
  4. Upgrade

    Upgrade Payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.27
  5. Configuration

    Disable the Import Export plugin until upgrading.

    @payloadcms/plugin-import-export enabled = false
  6. Compensating control

    Restrict access to the Import Export plugin endpoints until upgrading.

Event History

Oct 6, 2026
CVE Published
via MITRE·03:57 PM
Data Sourced
via MITRE·03:57 PM
DescriptionWeakness
Advisory Published
via GitHub·04:09 PM
Data Sourced
via GitHub·04:09 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Only applications with @payloadcms/plugin-import-export enabled are affected. Applications that do not use this plugin are not affected.

2

Does exploitation require authentication or user interaction?

No. An unauthenticated attacker can submit prototype-sensitive field paths, and no user interaction is required.

3

What versions contain the fix?

Upgrade Payload packages to version 3.88.0 or later, or to 4.0.0-canary.27 or later. Affected releases include versions from 3.0.0 before 3.88.0 and canary releases before 4.0.0-canary.27.

4

What can be done if an upgrade cannot be applied immediately?

Disable the Import Export plugin or restrict access to its endpoints until the upgrade can be completed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203