EUVD-2026-16668Severity 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
Lifecycle Timeline
3DescriptionCVE.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 ('../').
AnalysisAI
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).
Technical ContextAI
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.
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.
Langflow before 1.3.0 allows unauthenticated remote code injection through the /api/v1/validate/code endpoint, enabling
Account takeover and remote code execution in Langflow AI workflow platform versions ≤1.6.9 due to a CORS misconfigurati
Langflow has a third RCE vulnerability via exec_globals (EPSS 10.0%) allowing inclusion of untrusted code that executes
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
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
An unauthenticated shell injection vulnerability exists in Langflow's GitHub Actions CI/CD workflows, allowing attackers
Langflow versions prior to 1.0.13 suffer from a Privilege Escalation vulnerability, allowing a remote and low privileged
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
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today