dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-6612

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in TransformerOptimus SuperAGI up to 0.0.14. This impacts the function get_agent_execution/update_agent_execution of the file superagi/controllers/agent_execution.py of the component Agent Execution Endpoint. Executing a manipulation of the argument agent_execution_id can lead to authorization bypass. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SuperAGI versions up to 0.0.14 contain an insecure direct object reference (IDOR) vulnerability in the agent_execution.py controller. The get_agent_execution and update_agent_execution functions fail to properly validate that the authenticated user owns or has access to the specified agent_execution_id, allowing attackers to access or modify other users' agent executions by manipulating this parameter.

MitigationImplement proper authorization checks in the affected functions to verify the requesting user owns or has permission to access the specific agent_execution_id before returning or modifying any execution data. Consider adding consistent ownership validation middleware for all agent execution endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SuperAGI version
    Locate the version file or check package metadata (e.g., version.py, setup.py, __init__.py, or requirements.txt in the SuperAGI installation directory) and compare the installed version to the affected range (all versions up to and including 0.0.14)
    Affected if Installed version is 0.0.14 or earlier, or version cannot be determined but the software is SuperAGI up to 0.0.14
  2. Locate agent_execution.py
    Find the agent_execution.py file in the SuperAGI source code, typically under a 'controllers' or similar directory
    Affected if The file exists in the codebase
  3. Inspect get_agent_execution function
    Open agent_execution.py and examine the get_agent_execution function. Look for authorization logic that validates the requesting user owns or has permission to access the agent_execution_id (such as checking user_id, account_id, or similar ownership fields before returning execution data)
    Affected if The function returns execution data without verifying the authenticated user owns or has access to the requested agent_execution_id
  4. Inspect update_agent_execution function
    Open agent_execution.py and examine the update_agent_execution function. Look for authorization logic that validates the requesting user owns or has permission to modify the agent_execution_id before allowing updates
    Affected if The function allows modifications without verifying the authenticated user owns or has access to the requested agent_execution_id

You are affected if SuperAGI version is 0.0.14 or earlier AND the get_agent_execution or update_agent_execution functions in agent_execution.py lack ownership validation for the agent_execution_id parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks in the affected functions to verify the requesting user owns or has permission to access the specific agent_execution_id before returning or modifying any execution data. Consider adding consistent ownership validation middleware for all agent execution endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6612 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data