dbcve.org
SuperagiApplication

CVE-2025-6280

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-19
Fix available
A fix is available. Upgrade to after 0.0.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 vulnerability, which was classified as critical, was found in TransformerOptimus SuperAGI up to 0.0.14. Affected is the function download_attachment of the file SuperAGI/superagi/helper/read_email.py of the component EmailToolKit. The manipulation of the argument filename leads to path traversal. The exploit has been disclosed to the public and may be used.

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 confidence

Path traversal vulnerability in the download_attachment function within SuperAGI/superagi/helper/read_email.py allows remote attackers to read arbitrary files on the host system by manipulating the filename parameter passed to the EmailToolKit component.

MitigationImplement strict input validation on the filename parameter to restrict path traversal sequences (../) and use secure file path resolution APIs (e.g., os.path.realpath) to ensure accessed files fall within the intended directory.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SuperagiApplication
Affected:<= 0.0.14

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
High
Integrity
High
Availability
High

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

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
    Run 'pip show superagi' or check the version in your package manager to identify the installed version of SuperAGI
    Affected if The installed version is less than or equal to 0.0.14
  2. Locate vulnerable source file
    Verify the presence of the file superagi/helper/read_email.py in your SuperAGI installation directory
    Affected if The file superagi/helper/read_email.py exists in your environment
  3. Identify EmailToolKit usage
    Search your codebase or configuration for instances where EmailToolKit is imported or utilized, particularly the download_attachment function
    Affected if EmailToolKit with download_attachment functionality is being used in your deployment
  4. Check if attachment download is exposed
    Examine how the filename parameter flows into the download_attachment function and whether external input can reach it without validation
    Affected if User-supplied filename input can reach the download_attachment function without sanitization

You are affected if SuperAGI version is 0.0.14 or lower and the EmailToolKit component with the vulnerable download_attachment function is accessible to users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.0.14
Interim mitigation

Implement strict input validation on the filename parameter to restrict path traversal sequences (../) and use secure file path resolution APIs (e.g., os.path.realpath) to ensure accessed files fall within the intended directory.

Recommended fix Moderate confidence

Version 0.0.15 or later stable release (check GitHub releases)

  1. 1. Identify the current SuperAGI version by checking the version file or git tags
  2. 2. Review the SuperAGI GitHub repository for releases newer than 0.0.14 that address security fixes
  3. 3. If a newer stable release (version 0.0.15 or later) is available, upgrade to that version following standard upgrade procedures
  4. 4. After upgrade, verify the fix by checking that the download_attachment function in superagi/helper/read_email.py properly sanitizes the filename parameter to prevent path traversal (e.g., using os.path.basename or similar)
  5. 5. Test the email attachment download functionality to confirm it works correctly with the fix in place
Caveat Review release notes for any breaking changes between 0.0.14 and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superagi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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