# CVE-2026-34751: Payload has Unvalidated Input in Password Recovery Endpoints

> Unauthenticated attackers can perform actions on behalf of users initiating password resets in Payload CMS due to unvalidated input.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2026
- **Updated:** 4 Apr 2026
- **Also known as:** GHSA-hp5w-3hxx-vmwf

## What is CVE-2026-34751?

CVE-2026-34751 is a critical authentication bypass vulnerability in payloadcms payload, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Payload is a free and open source headless content management system. Prior to version 3.79.1 in @payloadcms/graphql and payload, a vulnerability in the password recovery flow could allow an unauthenticated attacker to perform actions on behalf of a user who initiates a password reset. This issue has been patched in version 3.79.1 for @payloadcms/graphql and payload.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2026-34751?

4 open source packages ship an affected version, including @payloadcms/graphql and payload. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@payloadcms/graphql` | npm | All versions | 3.79.1 |
| `@payloadcms/graphql` | npm | All versions | 3.79.1 |
| `payload` | npm | All versions | 3.79.1 |
| `payload` | npm | All versions | 3.79.1 |

Products: Payloadcms Payload.

## How do I fix CVE-2026-34751?

Upgrade @payloadcms/graphql to 3.79.1 or later.

## Is CVE-2026-34751 being exploited?

There is no known exploitation of CVE-2026-34751 in the wild and no public exploit code.

## Other vulnerabilities in payloadcms payload

- [CVE-2026-105857](https://insights.sbomify.com/CVE-2026-105857/): Payload: RCE in Payload Form Builder (critical 10.0)
- [CVE-2026-105859](https://insights.sbomify.com/CVE-2026-105859/): Payload: Unauthorized update to collection documents (critical 9.8)
- [CVE-2026-25544](https://insights.sbomify.com/CVE-2026-25544/): Payload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite Adapters (critical 9.8)
- [CVE-2022-27952](https://insights.sbomify.com/CVE-2022-27952/): Unrestricted Upload of File with Dangerous Type in Payload (critical 9.8)
- [CVE-2026-105851](https://insights.sbomify.com/CVE-2026-105851/): Payload: Field access control bypass on auth collections (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34751 and fix it if it is affected.

What it is: CVE-2026-34751 is a critical authentication bypass vulnerability in payloadcms payload, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34751 in the wild and no public exploit code.

Affected packages and fixed versions:
- @payloadcms/graphql (npm): affected all versions; fixed in 3.79.1
- @payloadcms/graphql (npm): affected all versions; fixed in 3.79.1
- payload (npm): affected all versions; fixed in 3.79.1
- payload (npm): affected all versions; fixed in 3.79.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34751/ (Markdown: https://insights.sbomify.com/CVE-2026-34751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34751
- OSV: https://osv.dev/vulnerability/CVE-2026-34751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34751/
Summaries are generated and may contain mistakes; the official description above is the record.