All vulnerabilities
CVE-2026-105853GHSA-xgv3-crq2-6f69

Payload: Token refresh and password reset responses may expose restricted user fields

payloadcms payloadnpmLibraries & packages
CVSS
7.1High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.26%Chance of exploitation activity in the next 30 days, higher than 16% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in3.90.0Also 4.0.0-canary.34GitHub
Published6 Oct 2026Updated 9 Oct 2026CVE List

What fixes it

  • 3.90.0payload, npmGitHubnpm install payload@3.90.0
  • 4.0.0-canary.34payload, npmGitHubnpm install payload@4.0.0-canary.34

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Impact

Token refresh and password reset responses could return fields that the requesting user did not have access to.

You are affected if:

  • An authentication collection contains hidden or read-restricted fields.

Patches

Authentication responses now apply field access and hidden-field filtering before returning user documents. Full user documents remain available server-side for access control.

Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

Custom authentication strategies remain responsible for filtering user documents returned through custom responses.

Workarounds

There is no complete workaround. Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

Text from GitHub Advisory Database

Affected versions 6

  • payload, npm>= 3.0.0, < 3.90.0GitHub
  • payload, npm>= 4.0.0-canary.0, < 4.0.0-canary.34GitHub
  • payloadaffected: >= 3.0.0, < 3.90.0CVE List
  • payloadaffected: >= 4.0.0-canary.0, < 4.0.0-canary.34CVE List
  • payload, npmfrom 3.0.0, fixed in 3.90.0OSV
  • payload, npmfrom 4.0.0-canary.0, fixed in 4.0.0-canary.34OSV

References 4