{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3409 exists.","fix":"No fix has been published for CVE-2026-3409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3409 is a medium-severity code injection vulnerability in eosphoros-ai db-gpt, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3409 and fix it if it is affected.\n\nWhat it is: CVE-2026-3409 is a medium-severity code injection vulnerability in eosphoros-ai db-gpt, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3409 exists.\n\nAffected product: eosphoros-ai db-gpt. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3409/ (Markdown: https://insights.sbomify.com/CVE-2026-3409/index.md)","id":"CVE-2026-3409","markdown":"https://insights.sbomify.com/CVE-2026-3409/index.md","name":"CVE-2026-3409","record":{"aliases":["GHSA-3cpw-pmf6-39xg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"db-gpt web application","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via the Flow Import Endpoint in db-gpt by manipulating file inputs, requiring immediate mitigation due to public exploit availability.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"eosphoros-ai db-gpt Flow Import Endpoint import importlib.machinery.SourceFileLoader.exec_module code injection","id":"CVE-2026-3409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"itsourcecode Society Management System check_studid.php sql injection","id":"CVE-2026-3410"},"packages":[],"prev":{"headline":"Open Babel CDXML File atom.cpp GetExplicitValence null pointer dereference","id":"CVE-2026-3408"},"products":["db-gpt"],"published":"2026-03-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["eosphoros-ai"]},"summary":"Remote attackers can execute arbitrary code via the Flow Import Endpoint in db-gpt by manipulating file inputs, requiring immediate mitigation due to public exploit availability.","url":"https://insights.sbomify.com/CVE-2026-3409/"}