CVE-2026-6584
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 · uneditedA vulnerability was found in TransformerOptimus SuperAGI up to 0.0.14. This vulnerability affects the function update_user of the file superagi/controllers/user.py of the component User Update Endpoint. The manipulation of the argument user_id results in authorization bypass. The attack may be performed from remote. The exploit has been made public and could be used. 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 · high confidenceAuthorization bypass in the SuperAGI user update endpoint (superagi/controllers/user.py). The update_user function fails to properly validate that the requesting user has permission to modify the target user, allowing attackers to manipulate the user_id parameter to update arbitrary user accounts.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SuperAGI installationLocate the SuperAGI application directory or check running services that serve the SuperAGI web interface. Look for the superagi/ directory structure.Affected if SuperAGI is installed and running
-
Identify installed SuperAGI versionCheck the version file (typically version.py, __init__.py, or pyproject.toml in the SuperAGI root directory) or run: pip show superagi or docker images for the SuperAGI version tag.Affected if The installed version cannot be compared to any fixed range (no version data provided)
-
Locate vulnerable endpoint fileVerify the existence of superagi/controllers/user.py in the installation directory and confirm the update_user function is present.Affected if The file superagi/controllers/user.py exists with an update_user function
-
Inspect update_user authorization logicOpen superagi/controllers/user.py and examine the update_user function. Look for authorization checks that verify the requesting user has permission to modify the target user_id (e.g., checking current_user.id == user_id or role-based access control).Affected if The update_user function lacks or has weak authorization validation before modifying user data
-
Test endpoint behavior (if possible)If you have access to the application, attempt a request to the user update endpoint (typically POST /user or /user/update) with a user_id different from your authenticated session to see if you can modify another user's profile.Affected if The endpoint allows modification of users other than the authenticated user
A user is affected if SuperAGI is installed and the update_user function in superagi/controllers/user.py does not properly validate that the authenticated user has permission to modify the specified user_id parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks in the update_user function to verify the authenticated user has permission to modify the specified user_id. Consider adding role-based access control (RBAC) and ownership verification before allowing any user profile modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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