How severe is GHSA-w84c-53h3-mc2g?

GHSA-w84c-53h3-mc2g has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-w84c-53h3-mc2g?

GHSA-w84c-53h3-mc2g affects the following packages: payload (npm), payload (npm), @payloadcms/next (npm), @payloadcms/next (npm). Ecosystems affected: npm.

How do I fix GHSA-w84c-53h3-mc2g?

Update payload to 3.88.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w84c-53h3-mc2g is resolved across your whole dependency graph.

How do I detect GHSA-w84c-53h3-mc2g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w84c-53h3-mc2g if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-w84c-53h3-mc2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-w84c-53h3-mc2g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w84c-53h3-mc2g?

GHSA-w84c-53h3-mc2g has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w84c-53h3-mc2g?

GHSA-w84c-53h3-mc2g is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w84c-53h3-mc2g published, and has it been updated?

GHSA-w84c-53h3-mc2g was published on October 6, 2026 and was last updated on October 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Payload: Untrusted redirect URL parameter exploitGHSA-w84c-53h3-mc2g

MEDIUMFix: payloadcms/payload@a742140

GHSA-w84c-53h3-mc2g is a medium-severity (CVSS 6.1) Open Redirect vulnerability in payload. A fix is available for payload — see the affected versions and patch details below.

Also known asCVE-2026-105846

Published

Oct 6, 2026

Updated

Oct 6, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w84c-53h3-mc2g.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-w84c-53h3-mc2g by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

115other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

payloadnpm

629Kdownloads / week

@payloadcms/nextnpm

593Kdownloads / week

Description

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 Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`payload`	≥ 3.40.0&&< 3.88.0	3.88.0`npm install payload@3.88.0`
📦npm	`payload`	≥ 4.0.0-canary.0&&< 4.0.0-canary.27	4.0.0-canary.27`npm install payload@4.0.0-canary.27`
📦npm	`@payloadcms/next`	≥ 3.31.0&&< 3.88.0	3.88.0`npm install @payloadcms/next@3.88.0`
📦npm	`@payloadcms/next`	≥ 4.0.0-canary.0&&< 4.0.0-canary.27	4.0.0-canary.27`npm install @payloadcms/next@4.0.0-canary.27`

Affected Products

1 product · 28 configurations

Application

payloadpayloadcms

≥ 3.40.0 && < 3.88.0

1 version

4.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update payload to 3.88.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w84c-53h3-mc2g is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### 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.