VulnerabilityPublished 29 Oct 2026

CVE-2026-51903: SuperAGI v0.0.14 contains an improper access control

Source CVE Database V5

Compare

Not known to be exploited.

Data as of 29 Oct 2026, 18:49 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Since the vulnerability requires authentication, organizations should review and restrict access controls around project data endpoints. Monitor vendor advisories for any forthcoming patches or updates addressing this issue. Until a fix is available, limit user permissions to the minimum necessary to reduce exposure.

Description

SuperAGI version 0.0.14 has an improper access control vulnerability in the get_agent_by_latest_execution function. This flaw allows a remote authenticated attacker from one organization to access the latest execution and agent metadata of another organization's project by supplying the victim's project ID in a specific API endpoint.

Impact

An authenticated attacker can access sensitive metadata related to the latest execution and agent of projects belonging to other organizations. This unauthorized data disclosure could lead to information leakage about project activities and agent configurations, potentially aiding further attacks or reconnaissance. There is no indication of code execution or privilege escalation from the provided data.

References

Community reviews

Loading reviews…