GHSA-w84c-53h3-mc2g: Medium severity npm/@payloadcms/next vulnerability

Published Oct 6, 2026
·
Updated

Impact Under certain conditions, an attacker can craft a redirect link that sends a guest user to an untrusted destination after authenticating.

Patches Users should upgrade Payload packages to >= 3.88.0 or >= 4.0.0-canary.27.

Workarounds Upgrading is recommended. Until then, remove user-controlled redirect values from authentication flows or restrict them to known local paths.

Affected Software

4 affected componentsFixes available
npm/@payloadcms/next>=4.0.0-canary.0<4.0.0-canary.27
4.0.0-canary.27
npm/@payloadcms/next>=3.31.0<3.88.0
3.88.0
npm/payload>=4.0.0-canary.0<4.0.0-canary.27
4.0.0-canary.27
npm/payload>=3.40.0<3.88.0
3.88.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@payloadcms/next to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.27
  2. Upgrade

    Upgrade npm/@payloadcms/next to a version that resolves this vulnerability.

    Fixed in 3.88.0
  3. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.27
  4. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 3.88.0
  5. Upgrade

    Upgrade Payload packages to a version that resolves this vulnerability.

    Fixed in 3.88.0
  6. Upgrade

    Upgrade Payload packages to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.27
  7. Compensating control

    Remove user-controlled redirect values from authentication flows, or restrict redirect destinations to known local paths.

Event History

Oct 6, 2026
Advisory Published
via GitHub·04:09 PM
Data Sourced
via GitHub·04:09 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using the affected Payload packages are exposed when their authentication flow accepts user-controlled redirect values. A guest user can be redirected to an untrusted destination after authenticating.

2

What does an attacker need to exploit it?

The attacker needs to craft a redirect link and induce a guest user to use it during authentication. No attacker privileges are required, but user interaction is required.

3

What should we do if we cannot upgrade immediately?

Remove user-controlled redirect values from authentication flows, or restrict redirect targets to known local paths. Upgrading remains the recommended remediation.

4

Which versions contain the fix?

Upgrade Payload packages to version 3.88.0 or later, or to 4.0.0-canary.27 or later.

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