{"answers":{"affected":"3 open source packages ship an affected version, including langflow.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6597 exists.","fix":"No fix has been published for CVE-2026-6597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6597 is a medium-severity vulnerability in langflow-ai langflow, published on 20 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6597 and fix it if it is affected.\n\nWhat it is: CVE-2026-6597 is a medium-severity vulnerability in langflow-ai langflow, published on 20 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6597 exists.\n\nAffected packages and fixed versions:\n- langflow (PyPI): affected all versions up to 1.8.3; no fix listed\n- langflow (PyPI): affected all versions up to 1.8.3; no fix listed\n- langflow (PyPI): affected all versions up to 1.8.3; no fix listed\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-6597/ (Markdown: https://insights.sbomify.com/CVE-2026-6597/index.md)","id":"CVE-2026-6597","markdown":"https://insights.sbomify.com/CVE-2026-6597/index.md","name":"CVE-2026-6597","record":{"aliases":["GHSA-5jjf-wcvf-923w","PYSEC-2026-2565"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Langflow AI platform","requires_auth":"high_privilege","summary":"Remote attackers can access unprotected stored API credentials in Langflow due to improper handling in the Flow Using API component.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"},{"id":"CWE-255","name":null}],"description":"A weakness has been identified in langflow-ai langflow up to 1.8.3. Impacted is the function remove_api_keys/has_api_terms of the file src/backend/base/langflow/api/utils/core.py of the component Flow Using API. This manipulation causes unprotected storage of credentials. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"langflow-ai langflow Flow Using API core.py has_api_terms credentials storage","id":"CVE-2026-6597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"langflow-ai langflow Project Creation Endpoint projects.py encrypt_auth_settings cleartext storage in file","id":"CVE-2026-6598"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.8.3"],"package":"langflow","purl":null,"source":"GHSA-5jjf-wcvf-923w"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.8.3"],"package":"langflow","purl":"pkg:pypi/langflow","source":"GHSA-5jjf-wcvf-923w"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.8.3"],"package":"langflow","purl":"pkg:pypi/langflow","source":"PYSEC-2026-2565"}],"prev":{"headline":"langflow-ai langflow API Endpoint endpoints.py create_upload_file unrestricted upload","id":"CVE-2026-6596"},"products":["langflow"],"published":"2026-04-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["langflow-ai"]},"summary":"Remote attackers can access unprotected stored API credentials in Langflow due to improper handling in the Flow Using API component.","url":"https://insights.sbomify.com/CVE-2026-6597/"}