Quick answers
- Is CVE-2026-51901 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51901 being exploited in the wild.
- How severe is CVE-2026-51901?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- SuperAGI up to 0.0.14.
- Is there a fix for CVE-2026-51901?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-51901 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51901?
- Check whether you run SuperAGI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The /api/agentexecutions/schedule endpoint fails to verify that the supplied agent_id belongs to the authenticated user's organization before allowing execution scheduling. An authenticated attacker can enumerate agent IDs from other organizations and submit schedule requests that the endpoint accepts without authorization checks. The vulnerability exists in superagi/controllers/agent_execution.py:schedule_existing_agent and stems from missing tenant binding in the authorization logic.
Affected products
- SuperAGI SuperAGI up to 0.0.14
Timeline
- 2026-05-27: disclosed: Issue opened on GitHub
- 2026-10-02: advisory