CVE-2026-12942 is a path traversal vulnerability in Langflow affecting versions 1.0.0 through 1.10.1, scored CVSS 7.5. The EPSS of 0.00416 suggests low near-term exploitation probability—but this disconnect deserves scrutiny rather than dismissal.
The critical question is whether this traversal lives in a traditional HTTP route handler or in the serialization layer where Langflow deserializes workflow JSON definitions. If the vulnerability originates in the workflow import/deserialization pipeline rather than URL parsing, exploitation doesn't require sending /../ in a request—it requires a user with workflow creation or import privileges embedding a path traversal payload in a workflow definition that gets written to disk during deserialization. That fundamentally changes the threat model: CVSS assumes unauthenticated network exposure, but actual exploitation may require authenticated access to workflow management features, making the Auth metric potentially miscalibrated.
The version range spanning 1.0.0 through 1.10.1 is analytically significant. When the same vulnerability class persists across years of releases and architectural changes, it typically indicates the unsafe pattern lives in a utility layer—file-serving modules, serialization helpers, or import handlers—that every new feature inherits. A surgical patch to one route handler may not fix this; you need to trace where path resolution happens across the entire codebase and determine whether the same unsafe canonicalization exists in other file-handling paths.
The blast radius here is not arbitrary file read. It's the workflow graph itself: LLM prompts, API keys for model providers, chain configurations, and integration parameters serialized in JSON. If an attacker can traverse into the workflow storage layer, they access the entire configuration state of an AI orchestration stack without needing a separate credential theft vector. This makes the vulnerability asymmetrically valuable—every day an unpatched installation runs, it accumulates more sensitive workflows.
For defenders: verify whether the patch addresses a single endpoint or implements systemic path canonicalization across the file-serving architecture. If you deploy Langflow, audit your workflow storage directory for any unexpected files and review which users have workflow import permissions. The EPSS may be low now, but this reflects the vulnerability's obscurity rather than its severity—sophisticated actors targeting AI infrastructure would find the workflow storage layer a high-value target.