dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-6582

HIGH · 7.3 CVSS v3.1 Published 2026-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 flaw has been found in TransformerOptimus SuperAGI up to 0.0.14. Affected by this issue is the function get_vector_db_details of the file superagi/controllers/vector_dbs.py of the component Vector Database Management Endpoint. Executing a manipulation can lead to missing authentication. The attack can be executed remotely. The exploit has been published and may 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 · moderate confidence

The SuperAGI vector database management endpoint has a missing authentication vulnerability in the get_vector_db_details function within superagi/controllers/vector_dbs.py. Remote attackers can access sensitive vector database configuration details without any credentials, potentially exposing connection strings, credentials, and internal database metadata.

MitigationImplement authentication and authorization checks on the get_vector_db_details function and all vector database management endpoints. If a patch is unavailable in later versions, consider network-level restrictions or API gateway authentication enforcement.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify SuperAGI installation and version
    Locate the SuperAGI installation directory and check for version information in setup files, pyproject.toml, requirements.txt, or a VERSION file. Run: find / -name 'superagi' -type d 2>/dev/null or check common install paths like /opt/superagi, ~/superagi, or the current working directory.
    Affected if SuperAGI is installed and the version cannot be confirmed as patched, or the installed version predates the fix for CVE-2026-6582.
  2. Verify the vulnerable endpoint file exists
    Check for the presence of superagi/controllers/vector_dbs.py in the installation directory. This file contains the get_vector_db_details function referenced in the CVE.
    Affected if The file superagi/controllers/vector_dbs.py exists in the installation, indicating the vulnerable component is present.
  3. Inspect authentication on vector database endpoints
    Examine the vector_dbs.py file for authentication decorators (such as @login_required, @authenticate, or similar) applied to the get_vector_db_details function or the /vector_dbs routes. Search for decorators above the function definition.
    Affected if No authentication decorator is present on the get_vector_db_details function, or the endpoint lacks authorization checks.
  4. Test endpoint accessibility without credentials
    If the service is running, make an HTTP request to the vector database details endpoint (typically /api/vector_dbs or /vector_db_details) without providing any authentication tokens or headers. Use: curl -s http://localhost:8000/api/vector_dbs or the appropriate base URL.
    Affected if The endpoint returns vector database configuration details, connection strings, or credentials without requiring authentication.
  5. Review API routing configuration
    Examine the main application routing (often in main.py, app.py, or urls.py) to see how /api/vector_dbs routes are registered and whether any middleware or route guards apply authentication globally.
    Affected if The vector database endpoints are registered without being protected by authentication middleware or route guards.

You are affected if SuperAGI is installed, the get_vector_db_details endpoint in superagi/controllers/vector_dbs.py lacks authentication decorators, and the endpoint returns sensitive database configuration data when accessed without credentials.

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 authentication and authorization checks on the get_vector_db_details function and all vector database management endpoints. If a patch is unavailable in later versions, consider network-level restrictions or API gateway authentication enforcement.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6582 — 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-6582 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