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

Advisory record · `GHSA-xgv3-crq2-6f69`

- **Identifiers:** `GHSA-xgv3-crq2-6f69` · `CVE-2026-105853`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Oct 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `payload` (npm): affected `>=3.0.0, <3.90.0 || >=4.0.0-canary.0, <4.0.0-canary.34`; fixed in `3.90.0`, `4.0.0-canary.34`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Payload, an npm package, is affected in versions from 3.0.0 before 3.90.0 and from 4.0.0-canary.0 before 4.0.0-canary.34. Token refresh and password reset responses could include fields that the requesting user should not be able to read, and this applies when an authentication collection has hidden or read-restricted fields. The source does not describe the attacker's prerequisites beyond that. Upgrade to 3.90.0 or 4.0.0-canary.34; the source says there is no complete workaround.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 17th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:34 UTC: First seen by agentprime
- 31 Oct 2026, 13:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xgv3-crq2-6f69)

## Sources

- [GitHub Advisory Database: GHSA-xgv3-crq2-6f69](https://github.com/advisories/GHSA-xgv3-crq2-6f69)
- [OSV: GHSA-xgv3-crq2-6f69](https://osv.dev/vulnerability/GHSA-xgv3-crq2-6f69)
- <https://github.com/payloadcms/payload/security/advisories/GHSA-xgv3-crq2-6f69>
- <https://github.com/payloadcms/payload/commit/f5f1283d275c58b30e2faa6be7cdc4d49451ea91>
- <https://github.com/payloadcms/payload>
- <https://github.com/payloadcms/payload/releases/tag/v3.90.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xgv3-crq2-6f69>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xgv3-crq2-6f69/>. Everything for agents: <https://agentprime.io/llms.txt>.