Security Digest · Vulnerability record

CVE-2026-105857: Payload Form Builder has an RCE issue

Payload is a free and open source headless content management system.

CVSS 10.0 Critical EPSS 0.4% · p37

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.4%, percentile 37: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 37% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes @payloadcms/plugin-form-builder (npm) < 3.90.0, fixed in 3.90.0; @payloadcms/plugin-form-builder (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34, fixed in 4.0.0-canary.34. Check your lockfile, including transitive dependencies.

What it is

Payload is a free and open source headless content management system. In @payloadcms/plugin-form-builder versions before 3.90.0 and canary versions before 4.0.0-canary.34, an attacker can craft a form submission that executes code remotely on the server. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

From the GitHub advisory

Impact

A vulnerability in @payloadcms/plugin-form-builder in versions

You are affected if:

- You are using @payloadcms/plugin-form-builder

Patches

Weakness type: CWE-94, CWE-1321.

Product: @payloadcms/plugin-form-builder (npm) · Assigned by: GitHub_M · Published: 2026-10-06

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npm@payloadcms/plugin-form-builder< 3.90.03.90.0
npm@payloadcms/plugin-form-builder>= 4.0.0-canary.0, < 4.0.0-canary.344.0.0-canary.34
VendorProductAffected versions (per CVE record)
payloadcmspayload< 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34

Severity scores

Scored byCVSSScoreVector
GitHub_M3.110 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub3.110.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.43% probability of exploitation activity in the next 30 days; percentile 37.

Timeline

  • — CVE record last updated
  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-r488-j9vj-wx3q published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-r488-j9vj-wx3q github.com
  2. CVE.org record CVE-2026-105857 cve.org
  3. NVD entry CVE-2026-105857 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com

Critical npm advisories · Today’s Security Digest