dbcve.org
InjectionWeakness · CWE-74

CVE-2026-3409

HIGH · 7.3 CVSS v3.1 Published 2026-03-02
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 security flaw has been discovered in eosphoros-ai db-gpt 0.7.5. Affected is the function importlib.machinery.SourceFileLoader.exec_module of the file /api/v1/serve/awel/flow/import of the component Flow Import Endpoint. Performing a manipulation as part of File results in code injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. 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

Code injection vulnerability in db-gpt 0.7.5's Flow Import Endpoint (/api/v1/serve/awel/flow/import) allows remote attackers to inject malicious Python code via the importlib.machinery.SourceFileLoader.exec_module function during file import operations. The lack of input validation on imported files enables arbitrary code execution.

MitigationImplement strict validation of imported files (whitelist allowed file types, verify file content/magic bytes) and use safe deserialization/import mechanisms instead of direct exec_module calls. Consider implementing a sandboxed execution environment for imported code or disabling the import functionality until a proper fix is available.

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. Confirm db-gpt installation and version
    Run 'pip show db-gpt' or check your package manager to retrieve the installed version of db-gpt
    Affected if The installed version is 0.7.5 exactly or falls within the 0.7.x range prior to any available patch
  2. Identify if the AWEL flow import endpoint is exposed
    Check your API routes or reverse proxy configuration for the path '/api/v1/serve/awel/flow/import' and verify it is accessible
    Affected if The endpoint is reachable without additional authentication or network segmentation
  3. Locate the flow import module
    Search for files containing 'awel' and 'flow' import functionality in the db-gpt installation directory, typically under a 'serve' or 'api' folder
    Affected if The module importlib.machinery.SourceFileLoader is used directly in the flow import handling code
  4. Check for input validation on flow imports
    Review the flow import handler code for validation of uploaded files, file type checking, or content verification before passing to exec_module
    Affected if No whitelist of allowed file types, no magic byte verification, and no sandboxing is present in the import logic
  5. Verify execution context of imported modules
    Inspect whether the flow import functionality runs exec_module on user-supplied files without sanitization or sandboxing
    Affected if The code directly calls exec_module on imported files without using safe deserialization or a restricted import mechanism

You are affected if db-gpt version 0.7.5 is installed and the /api/v1/serve/awel/flow/import endpoint is accessible without the code performing strict validation on imported files before exec_module execution.

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 strict validation of imported files (whitelist allowed file types, verify file content/magic bytes) and use safe deserialization/import mechanisms instead of direct exec_module calls. Consider implementing a sandboxed execution environment for imported code or disabling the import functionality until a proper fix is available.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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