Open Redirect Affecting @payloadcms/next package, versions >=3.31.0 <3.88.0>=4.0.0-canary.0 <4.0.0-canary.27


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.23% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Open Redirect vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JS-PAYLOADCMSNEXT-20571761
  • published8 Oct 2026
  • disclosed6 Oct 2026
  • creditkullai-secasure, yuvraj-secasure

Introduced: 6 Oct 2026

NewCVE-2026-105846  (opens in a new tab)
CWE-601  (opens in a new tab)

How to fix?

Upgrade @payloadcms/next to version 3.88.0, 4.0.0-canary.27 or higher.

Overview

Affected versions of this package are vulnerable to Open Redirect through the getSafeRedirect utility in packages/payload/src/utilities/getSafeRedirect.ts and the authentication forms in examples/auth/src/app/(app)/login/LoginForm/index.tsx and examples/auth/src/app/(app)/create-account/CreateAccountForm/index.tsx. An attacker can send a crafted redirect value to a login or account-creation flow and cause a guest user to be sent to an untrusted destination after authenticating. The vulnerable code accepts redirect input from useSearchParams() and passes it to router.push() without restricting it to a known local path, so a malicious link can steer the post-login navigation away from the intended account page. This can be used for phishing and trust abuse by making an authentication link redirect the user to an attacker-controlled site after sign-in.

Workarounds

  • Remove user-controlled redirect values from the authentication login and account-creation flows, or restrict redirect to known local paths only, so attackers cannot steer users to an untrusted destination after sign-in.

CVSS Base Scores

version 4.0
version 3.1