CVE-2026-105859

validatedZero produced an exploit or a check.

GHSA-f7hx-52q9-hcrf ↗EUVD-2026-93503 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
payloadcms payload < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34
fixed in 3.90.0, 4.0.0-canary.34
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-822, permanent identifier
pkg:npm/payload
+2.4dTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+2.4dagent stopped
0
+1d
+2d

description

Payload installations using orderable: true on a collection or join field are affected. An attacker able to send a request to the affected update endpoint may modify collection documents without collection-level or field-level authorization checks.

mitigation

Upgrade the payload package to version 3.90.0 or later, or to 4.0.0-canary.34 or later for the canary release line. Until upgraded, disable orderable on affected collection and join fields where feasible.

fixed in 3.90.0, 4.0.0-canary.34

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.35%27th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 16:31Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-06 16:31Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-105859

{
  "etk_id": "ETK-2026-822",
  "cve_id": "CVE-2026-105859",
  "display_id": "CVE-2026-105859",
  "ghsa_id": "GHSA-f7hx-52q9-hcrf",
  "euvd_id": "EUVD-2026-93503",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Access-control bypass in Payload collection updates",
  "summary": "Payload installations using `orderable: true` on a collection or join field are affected. An attacker able to send a request to the affected update endpoint may modify collection documents without collection-level or field-level authorization checks.",
  "mitigation": "Upgrade the `payload` package to version 3.90.0 or later, or to 4.0.0-canary.34 or later for the canary release line. Until upgraded, disable `orderable` on affected collection and join fields where feasible.",
  "vendor": "payloadcms",
  "product": "payload",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 3.90.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.90.0"
      ],
      "package_name": "payload",
      "purl": "pkg:npm/payload"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0-canary.0, < 4.0.0-canary.34"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "4.0.0-canary.34"
      ],
      "package_name": "payload",
      "purl": "pkg:npm/payload"
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0035,
  "epss_percentile": 0.2732,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 23.579253866666665,
  "t0_at": "2026-10-06T16:31:52.275000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-09T03:11:47.847823+00:00",
      "days": 2.4443932039699074,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T16:31:52.275000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-06T16:31:52.275000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T16:31:52.275000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105859"
    }
  }
}

published 2026-10-06 23:24Z
last change 2026-10-21 18:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.