{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9138 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9138 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9138 and fix it if it is affected.\n\nWhat it is: CVE-2026-9138 is a medium-severity path traversal vulnerability in Langflow Langflow, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9138 in the wild and no public exploit code.\n\nAffected product: Langflow Langflow. 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-9138/ (Markdown: https://insights.sbomify.com/CVE-2026-9138/index.md)","id":"CVE-2026-9138","markdown":"https://insights.sbomify.com/CVE-2026-9138/index.md","name":"CVE-2026-9138","record":{"aliases":["GHSA-44jp-wv2q-qjwp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Langflow OSS","requires_auth":"low_privilege","summary":"Authenticated attackers can write or delete arbitrary files via path traversal in Langflow, potentially leading to server compromise.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"langflow","vendor":"langflow"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"IBM Langflow OSS 1.0.0 through 1.11.2 Langflow could allow an authenticated attacker to write arbitrary files to the server due to improper input validation in the SaveToFileComponent. The application constructs local file paths using attacker‑controlled input without sufficient sanitization when handling requests to the /api/v1/run/{flow_id} endpoint. An attacker with low‑privileged authenticated access (such as a valid API key or user session) can supply crafted path values, including absolute paths or path traversal sequences, allowing arbitrary file writes to locations writable by the Langflow process. Successful exploitation may lead to unauthorized file creation or modification, potentially resulting in further compromise depending on the deployment environment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in Langflow OSS","id":"CVE-2026-9138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"langflow:langflow","products":["langflow:langflow"],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Taiko AG1000-01A Rev 7.3/8 Hard-coded Credentials via login.zhtml","id":"CVE-2026-9139"},"packages":[],"prev":{"headline":"CSP Report Endpoint Log Flooding in MISP via Incorrect Size Limit","id":"CVE-2026-9137"},"products":["Langflow OSS"],"published":"2026-09-04","related":[{"cvss_score":9.8,"headline":"IBM Langflow Code Injection","id":"CVE-2026-9198","kev_date_added":"2026-08-04","published":"2026-07-17"},{"cvss_score":9.8,"headline":"Langflow Inclusion of Functionality from Untrusted Control Sphere","id":"CVE-2026-0770","kev_date_added":"2026-07-21","published":"2026-01-23"},{"cvss_score":9.8,"headline":"Langflow Missing Authentication","id":"CVE-2025-3248","kev_date_added":"2025-05-05","published":"2025-04-07"},{"cvss_score":9.4,"headline":"Langflow Origin Validation Error","id":"CVE-2025-34291","kev_date_added":"2026-05-21","published":"2025-12-05"},{"cvss_score":9.3,"headline":"Langflow Code Injection","id":"CVE-2026-33017","kev_date_added":"2026-03-25","published":"2026-03-20"},{"cvss_score":8.4,"headline":"Langflow Authorization Bypass Through User-Controlled Key","id":"CVE-2026-55255","kev_date_added":"2026-07-07","published":"2026-06-23"},{"cvss_score":10,"headline":"Unauthenticated Server-Side RCE via PythonCodeStructuredTool in Public Flows","id":"CVE-2026-10134","kev_date_added":null,"published":"2026-06-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["IBM"]},"summary":"Authenticated attackers can write or delete arbitrary files via path traversal in Langflow, potentially leading to server compromise.","url":"https://insights.sbomify.com/CVE-2026-9138/"}