CVE-2026-51901

waiting for further signalsZero needs more public information before it can validate it.

GHSA-mv3w-9m62-vw4g ↗EUVD-2026-91703 ↗

no check availablenot proven exploitable
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.
SuperAGI n/a
CWE-284 Improper Access Control
ETK-2026-583, permanent identifier
15d 18h 39msince last run
46mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+99h59m
0
+2h
+4h
+6h
+8h
+10h

description

SuperAGI versions through 0.0.14 do not properly scope agent-scheduling requests to the caller's organization. An authenticated user from one organization may trigger scheduling for an agent belonging to another organization when they can reach the affected scheduling endpoint.

mitigation

Restrict or disable access to the agent-execution scheduling endpoint until organization ownership is enforced for every requested agent. Limit credentials for this function to trusted users and monitor scheduling activity for cross-organization requests.

check
no
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
46m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 00:00Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-02 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-583",
  "cve_id": "CVE-2026-51901",
  "display_id": "CVE-2026-51901",
  "ghsa_id": "GHSA-mv3w-9m62-vw4g",
  "euvd_id": "EUVD-2026-91703",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-organization authorization bypass in SuperAGI scheduling",
  "summary": "SuperAGI versions through 0.0.14 do not properly scope agent-scheduling requests to the caller's organization. An authenticated user from one organization may trigger scheduling for an agent belonging to another organization when they can reach the affected scheduling endpoint.",
  "mitigation": "Restrict or disable access to the agent-execution scheduling endpoint until organization ownership is enforced for every requested agent. Limit credentials for this function to trusted users and monitor scheduling activity for cross-organization requests.",
  "vendor": null,
  "product": "SuperAGI",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 8.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0025,
  "epss_percentile": 0.158,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 46.09046678333333,
  "t0_at": "2026-10-02T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-51901"
    }
  }
}

published 2026-10-04 19:42Z
last change 2026-10-21 15:29Z

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.