CVE-2026-6585
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 determined in TransformerOptimus SuperAGI up to 0.0.14. This issue affects the function update_organisation of the file superagi/controllers/organisation.py of the component Organisation Update Endpoint. This manipulation of the argument organisation_id causes authorization bypass. It is possible to initiate the attack 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 confidenceAn authorization bypass vulnerability exists in SuperAGI up to 0.0.14 in the organisation update endpoint (superagi/controllers/organisation.py, function update_organisation). By manipulating the organisation_id parameter, an authenticated attacker can modify organization data they should not have access to, bypassing the intended access control checks.
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.
-
Check the installed SuperAGI versionRun 'pip show superagi' or check the version in your package manager, requirements.txt, or setup.pyAffected if The version is 0.0.14 or lower (any version up to and including 0.0.14)
-
Locate the organisation controller fileFind the file superagi/controllers/organisation.py in your installation directoryAffected if The file exists in the installation
-
Inspect the update_organisation functionOpen organisation.py and locate the update_organisation function definitionAffected if The function exists in the file
-
Check for vulnerable organisation_id parameter handlingExamine the update_organisation function body for direct use of organisation_id parameter without validating that the authenticated user belongs to or has permission for that organisationAffected if The function accepts organisation_id as a parameter and uses it directly in database queries or updates without checking user-organisation membership or permission
-
Verify missing authorization logicSearch the update_organisation function for any authorization checks such as verifying user.organisation_id matches the requested organisation_id, or checking user roles/permissions before allowing updatesAffected if No such authorization validation exists in the function
You are affected if running SuperAGI version 0.0.14 or lower AND the update_organisation function in superagi/controllers/organisation.py processes the organisation_id parameter without verifying the authenticated user has permission to modify that specific organization.
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 validation in the update_organisation function to verify the authenticated user has permission to modify the specific organization identified by organisation_id before allowing any updates.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6585 — 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-6585 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