Summary
Payload: Remote Code Execution through first-register
Advisory details
Impact
A crafted request to the public first-register operation can be used to perform a RCE exploit.
You are affected if:
- You use local auth strategy and your application remains without an initial user created
Patches
In the patched version data submission to create first user is properly sanitized.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
References
- https://github.com/advisories/GHSA-97rh-rhh2-7vjv
- https://github.com/payloadcms/payload/security/advisories/GHSA-97rh-rhh2-7vjv
- https://nvd.nist.gov/vuln/detail/CVE-2026-105858
- https://github.com/payloadcms/payload/commit/e947fc4ba4a434f276d043386e501b1d14eda679
- https://github.com/payloadcms/payload/releases/tag/v3.90.0
Related vulnerabilities
All Supply chain →- CRITICALCVE-2026-105857
Payload Form Builder has an RCE issue
- CRITICALCVE-2026-104849
Tinypool: Prototype Pollution Gadget to RCE in run() options
- HIGHCVE-2026-102870
Microsoft Security Advisory CVE-2026-102870 - ASP.NET Core Remote Code Execution Vulnerability
- HIGHCVE-2026-108259
Tina: Code injection via unescaped Git branch name in generated client source
- CRITICALCVE-2026-107806
Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite
- HIGHCVE-2026-61433
PraisonAI: API deploy code generator embeds unescaped YAML fields into Python source