EUVD-2026-16668Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to API endpoint
-
ExploitSend POST request to /api/v2/files with path traversal sequences in filename parameter
-
ExecutionWrite malicious file to arbitrary filesystem location
-
ImpactExecute arbitrary code or access sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated user access to the target application. Attacker must send a crafted POST request to '/api/v2/files' endpoint with path traversal sequences ('../' or '..\') in the 'filename' parameter of multipart form data to write files to arbitrary filesystem locations. |
| Impact | Real-world risk is substantial based on multiple converging signals. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates a remotely exploitable vulnerability with low attack complexity requiring only low-level authenticated access, delivering high impact across confidentiality, integrity, and availability. Path traversal vulnerabilities are well-understood by attackers and relatively straightforward to exploit once discovered, as they require only crafting malicious filenames with directory traversal sequences. The requirement for authentication (PR:L) provides some risk mitigation by limiting the attack surface to credential holders, though compromised or insider accounts eliminate this barrier. No public exploit code has been identified at time of analysis, reducing immediate weaponization risk. EPSS probability data is not available in the provided intelligence. The vulnerability is not present in CISA's Known Exploited Vulnerabilities catalog, indicating no confirmed active exploitation campaigns. However, the combination of remote accessibility, low complexity, and critical impact (arbitrary file write can lead to code execution, data exfiltration, or system compromise) makes this a legitimate priority for organizations running affected software, particularly in internet-facing deployments or environments with untrusted authenticated users. |
| Exploit ScenarioDerived | An authenticated attacker with low-level API access crafts a malicious file upload request to POST /api/v2/files with a filename parameter containing path traversal sequences such as '../../../etc/cron.d/malicious' or '..\..\..\Windows\System32\evil.dll'. The vulnerable endpoint processes this unsanitized input and writes the uploaded file content to the specified location outside the intended upload directory. The attacker achieves arbitrary file write capability limited only by the application's filesystem permissions, enabling code execution through overwriting executable files, configuration injection via modifying application settings files, or persistence through placing files in startup directories. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 27, 2026
Arbitrary file write vulnerability in an API endpoint (POST /api/v2/files) enables authenticated remote attackers to overwrite critical system files or place malicious executables in startup directories through unvalidated filename parameters containing path traversal sequences. The vulnerability carries a CVSS score of 8.8 (High) with network-accessible attack vector requiring low-level privileges and no user interaction. No public exploit identified at time of analysis, though the straightforward nature of path traversal exploitation increases risk. Research disclosed by Tenable Security Research (TRA-2026-26).
RemediationAI
Consult the Tenable Security Research advisory TRA-2026-26 at https://www.tenable.com/security/research/tra-2026-26 for vendor-specific patch availability and upgrade guidance, as no fix version has been specified in the available intelligence. Until patching is confirmed and deployed, implement compensating controls including: enforce strict input validation on the filename parameter to reject any path traversal sequences (../, ..\, URL-encoded variants), implement allowlist validation restricting filenames to alphanumeric characters and safe punctuation, configure the application to write uploads to a dedicated directory with restricted permissions outside the webroot, and apply principle of least privilege to limit filesystem write access for the application service account. Network-level mitigations include restricting API access to authenticated users from trusted IP ranges and implementing API gateway rate limiting to prevent automated exploitation attempts. Monitor filesystem activity for suspicious file creation patterns in system directories.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability represents a classic path traversal weakness (CWE-22: Improper Limitation of a Pathname to a Restricted Directory) in a RESTful API file upload handler. The POST /api/v2/files endpoint accepts multipart form data containing a filename parameter but fails to sanitize or validate directory traversal sequences such as '../' before constructing filesystem paths. This allows attackers to escape intended upload directories and write to arbitrary locations within the application's filesystem access permissions. Path traversal vulnerabilities typically arise when applications concatenate user-controlled input directly into file path operations without canonicalization, boundary checks, or allowlist validation against permitted directories. The specific affected product has not been identified in the available intelligence, though Tenable's research disclosure (TRA-2026-26) suggests this was discovered through security research rather than incident response.
Know when Langflow gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (tenable) · only source for this CVE.
CVSS VectorVendor: tenable
DescriptionCVE.org
The 'POST /api/v2/files' endpoint does not sanitize the 'filename' parameter from the multipart form data, allowing an attacker to write files to arbitrary locations on the filesystem using path traversal sequences ('../').
Executive ViewAI
A high-severity arbitrary file write vulnerability in the POST /api/v2/files endpoint allows authenticated users to overwrite critical system files or inject malicious executables into startup directories through path traversal manipulation. Organizations using this API are at risk of privilege escalation, persistent code execution, and system compromise without compensating controls in place.
Implement network segmentation to restrict access to the POST /api/v2/files endpoint from untrusted sources; deploy WAF rules to block path traversal payloads (e.g., patterns containing '../', '..\', or URL-encoded equivalents); disable the file upload API endpoint entirely if business operations do not depend on it; enforce strict file system permissions to prevent overwrite of critical system executables and startup directories; implement file integrity monitoring (FIM) to detect unauthorized modifications to sensitive system files; audit all API calls to /api/v2/files and alert on anomalous filename patterns or paths outside expected directories.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Langflow before 1.3.0 allows unauthenticated remote code injection through the /api/v1/validate/code endpoint, enabling
Langflow has a third RCE vulnerability via exec_globals (EPSS 10.0%) allowing inclusion of untrusted code that executes
Account takeover and remote code execution in Langflow AI workflow platform versions ≤1.6.9 due to a CORS misconfigurati
Langflow has a code injection vulnerability in the code component (EPSS 2.6%) enabling remote code execution through the
Langflow has an eval injection in eval_custom_component_code (EPSS 2.0%) enabling remote code execution through crafted
Remote code execution in IBM Langflow OSS 1.0.0 through 1.9.3 lets an unauthenticated attacker inject and run arbitrary
Code injection in Langflow CSV Agent node before 1.8.0. The node hardcodes allow_dangerous_code=True, enabling arbitrary
Langflow through 0.6.19 allows remote code execution if untrusted users are able to reach the "POST /api/v1/custom_compo
OS command injection in Langflow's MCP stdio transport allows an attacker who can reach the MCP server configuration end
langflow <=1.0.18 is vulnerable to Remote Code Execution (RCE) as any component provided the code functionality and the
langflow v1.0.12 was discovered to contain a remote code execution (RCE) vulnerability via the PythonCodeTool component.
Langflow before 1.7.0.dev45 exposes multiple API endpoints without authentication, allowing unauthenticated access to us
GitHub PoC