Langflow Oss
Monthly
Authenticated remote code execution affects IBM Langflow OSS 1.0.0 through 1.12.2, where improper control of code generation lets any account with at least low privileges (CVSS PR:L, AV:N, UI:N) cause attacker-supplied code to run server-side on the Langflow host, yielding high confidentiality, integrity, and availability impact (CVSS 8.8). Exploitation is not possible against a default install without valid credentials, and no public exploit code or confirmed active exploitation was identified at time of analysis. The practical exposure therefore concentrates on internet-reachable or multi-tenant instances that permit self-registration or host untrusted users; isolated, single-tenant, network-restricted deployments with trusted operators carry substantially lower risk.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.2 lets any remote user holding a valid low-privileged account execute arbitrary code on the hosting server, with high impact to confidentiality, integrity, and availability (CVSS 8.8, PR:L, no user interaction required). The attack surface is the code path where special elements used in code are not properly neutralized (CWE-94), so deployments that allow untrusted or self-registered accounts to author and run flows are the most exposed, while instances with closed registration and no internet exposure are materially less at risk. No public exploit code has been identified at time of analysis, EPSS is only 0.58% (46th percentile), and CISA SSVC rates exploitation as 'none', making this a serious-but-not-emergency issue; a vendor patch is available per IBM's advisory.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows a low-privileged user to run arbitrary code because the platform improperly controls generation of executable code (CWE-94). Exploitation requires only a valid account on the instance (CVSS PR:L, AV:N, AC:L, UI:N), so an attacker who holds or obtains any credential able to create, import, or execute a flow/component that reaches the vulnerable code-generation path can achieve full confidentiality, integrity, and availability impact on the host. No public exploit code was identified at time of analysis, CISA's SSVC assessment records exploitation as "none", and EPSS is 0.58% (46th percentile), placing this as a genuinely serious but not emergency-tier issue whose real-world risk scales with how exposed the Langflow instance is and how freely low-privilege accounts are provisioned.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker with flow-authoring privileges to inject and execute arbitrary code through Langflow's code-generation mechanism (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as high severity (8.8), requiring network reachability, low privileges, and no user interaction; however, in typical deployments where flow creation or modification is broadly granted, the practical barrier may be lower than the PR:L metric implies. No public exploit code or CISA KEV entry has been identified at time of analysis, and EPSS is 0.61% (48th percentile); IBM has released a vendor patch.
Deserialization of untrusted cache data in IBM Langflow OSS 1.0.0 through 1.12.2 can execute attacker-controlled code with the privileges of the Langflow service process, but only for an attacker who has already obtained two things: the Langflow server secret and write access to the backing Redis instance used as the application cache. Because both prerequisites are effectively gated - the server secret is a trusted signing/trust value and Redis is normally bound to localhost or a private, authenticated network - this is not exploitable by an anonymous remote attacker against a default deployment, which is why the practical risk is lower than the 7.5 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Remote code execution can result in IBM Langflow OSS 1.0.0 through 1.12.2 through a dependency confusion weakness, where the product resolves an expected dependency from a public package registry instead of the intended trusted source. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates an unauthenticated remote attacker with no user interaction required, and the unpatched severity is rated 9.8; however, our independent assessment lowers the attack complexity to AC:H because successful exploitation depends on the attacker knowing or guessing the exact dependency name and on the victim's resolver preferring an attacker-published public package over the legitimate one, typically during an install, build, or import event rather than against a running service. There is no confirmed active exploitation (CISA KEV does not list this CVE), SSVC records Exploitation: none and Automatable: no, no public exploit code has been identified at time of analysis, and EPSS is only 0.68% (51st percentile), so the practical near-term risk is materially lower than the 9.8 headline suggests. A vendor patch is available per the IBM advisory.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, low-privilege authenticated attacker to retrieve objects belonging to other users by manipulating a user-controlled identifier that the application fails to scope to the requesting principal (CWE-639, IDOR-style authorization bypass). The flaw is network-reachable with low attack complexity and no user interaction, but it is gated on the attacker already holding valid credentials for a low-privilege account (CVSS PR:L); the assessed impact is a high-confidentiality, read-only exposure with no demonstrated integrity or availability effect, so realistic risk concentrates in multi-user or multi-tenant Langflow deployments where a low-trust account can reach another tenant's or user's data. Patch available per vendor advisory (IBM support node 7290694); no public exploit identified at time of analysis.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any attacker who can reach the service execute arbitrary operating system commands on the underlying host. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw requires no credentials, no user interaction, and no non-default configuration, so a default Langflow deployment exposed beyond localhost is directly exploitable. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); IBM has published a vendor advisory with a fix, and practical risk is concentrated in self-hosted developer instances that are bound to reachable interfaces rather than being restricted to localhost or placed behind authentication and firewalling.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who already holds a valid low-privilege session execute arbitrary code on the host by sending a crafted request that bypasses improper input validation. The flaw is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8), so the authentication requirement is the main barrier; deployments with open or self-service sign-up, internet exposure, or multi-tenant use carry the highest risk. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any holder of valid credentials - even a low-privileged one - submit or edit a flow that reaches the server-side code-generation and execution path, resulting in arbitrary OS command execution on the Langflow backend. IBM scores it 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and classifies the root cause as CWE-94 code injection; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so active exploitation is not confirmed. The decisive risk factor is deployment posture: internet-exposed or multi-tenant instances running with authentication disabled, default or shared credentials, or open self-registration collapse the PR:L barrier and behave like unauthenticated RCE targets.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any user who can log in to the instance run arbitrary code on the host, because the platform fails to properly constrain attacker-supplied input before it reaches a code-execution path. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning low-complexity, network-reachable exploitation that requires only a low-privileged account but yields full confidentiality, integrity, and availability impact - no user interaction and no elevated privileges are needed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, but IBM has published a vendor advisory with a fix, so the practical exposure is greatest for organizations that expose Langflow to untrusted networks or provision accounts broadly.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker to run arbitrary operating-system commands by supplying crafted input to a component that fails to neutralize special elements before passing them to an OS command or code-evaluation path (CWE-94). Per the assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires a valid low-privilege authenticated session on the Langflow instance, needs no victim interaction, and yields full confidentiality, integrity, and availability impact on the affected host. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the practical risk is concentrated on network-exposed Langflow servers that use weak, shared, or default credentials, since a compromised or low-privilege account is the only prerequisite.
Improper access control in the vertex result caching subsystem of IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote authenticated attacker read sensitive cached data or inject malicious content into vertex results that other users then consume. The issue carries a CVSS 3.1 base score of 8.3 (High) under the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, meaning it is network-reachable with low complexity and requires only a low-privileged account, while yielding high confidentiality and integrity impact and low availability impact. No public exploit code has been identified at time of analysis and the flaw does not appear in CISA KEV; IBM has published a patch advisory (node/7290694), so exposure is limited to unpatched deployments and to attackers who already hold valid credentials on the instance.
Authenticated remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where an incomplete blocklist in the built-in code security scanner can be bypassed to execute arbitrary code on the server. Exploitation requires a valid low-privilege account (CVSS PR:L) and the ability to submit code evaluated by the scanner; unauthenticated attackers are not sufficient. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the high CVSS base score of 8.8 and the multi-tenant exposure of typical Langflow deployments make the risk significant where untrusted users can register or be provisioned.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets an authenticated attacker escape the application's code execution sandbox and run arbitrary commands on the host. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) confirms network reachability and a low-privileged authenticated session as the only precondition, with no user interaction required. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the low complexity and high impact make this a genuine prioritization concern for internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows attackers to execute arbitrary code via improper control of code generation (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates remote, unauthenticated, low-complexity exploitation with full confidentiality, integrity, and availability impact, though the independent assessment notes the pre-auth condition is not independently confirmed by the description. A vendor patch is available, and no public exploit code has been identified at time of analysis; risk is highest for internet-exposed instances within the affected version range.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.11.5 is achievable by authenticated users who can submit custom component source code to the platform. The built-in static security scanner contains a logic error (CWE-693: Protection Mechanism Failure) in its alias-tracking path: when a dangerous callable is referenced indirectly through an annotated class-body assignment, the resolved callable is never validated against the blocklist, making the scan trivially bypassable with a crafted construct. If the malicious component reaches runtime execution, OS commands run in-process with the full privileges of the Langflow service account. No public exploit has been identified at time of analysis, but IBM has released a patch and the network-accessible, low-privilege attack surface makes this a meaningful risk in any multi-user or shared Langflow deployment.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows a low-privilege attacker to execute arbitrary OS commands by submitting crafted input that bypasses the platform's security scanner denylist. The root cause is an incomplete denylist (CWE-78) in the scanner responsible for gatekeeping executable content within AI workflow components - meaning certain command injection payloads are not intercepted and reach the underlying OS. No public exploit has been identified at time of analysis, though the authenticated-only barrier is a relatively low bar in multi-tenant or shared Langflow deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows authenticated network attackers to run arbitrary operating system commands by supplying crafted input to an unguarded eval() call within the application. The root cause is CWE-94 code injection - attacker-controlled data is passed directly to a dynamic evaluation function without sanitization or sandboxing. IBM has released a patch and no public exploit code or CISA KEV listing has been identified at time of analysis, but the straightforward nature of eval()-based injection and the low privilege bar (any authenticated user) make this a meaningful post-authentication escalation risk.
Authenticated remote code execution in IBM Langflow OSS 1.0.0-1.11.5 allows a low-privileged attacker to execute arbitrary OS commands by supplying malicious command-line arguments through the MCP stdio server configuration interface. The root cause (CWE-78: OS Command Injection) is insufficient sanitization of user-controlled argument strings before they are passed to a subprocess invocation, giving the attacker OS-level code execution within the application's security context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the authenticated-but-low-privilege attack path makes this a meaningful threat in multi-tenant or shared Langflow deployments.
Remote OS command execution in IBM Langflow OSS (versions 1.0.0 through 1.11.5) lets remote attackers run arbitrary operating-system commands due to improper neutralization of special elements passed into a shell command (CWE-78). Per the CVSS vector (PR:N/UI:N), exploitation requires no authentication or user interaction and yields full confidentiality, integrity, and availability impact on the host. No public exploit has been identified at time of analysis, though the vendor has released a patch.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows authenticated low-privileged users to execute arbitrary server-side code by exploiting an incomplete environment variable blocklist. The root cause (CWE-94, Code Injection) means the platform's intended restrictions on environment variable access can be circumvented by supplying references to variables omitted from the blocklist, resulting in full confidentiality, integrity, and availability compromise. No public exploit has been identified at time of analysis, and a vendor-released patch is available per IBM advisory node/7286666.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows an unauthenticated remote attacker to run arbitrary code by injecting malicious code that is evaluated during graph construction (CWE-94). Because Langflow is a visual framework for building LLM/agent workflows whose flows are assembled into executable graphs, a crafted flow definition submitted to the server is interpreted as code rather than data. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, network-reachable, unauthenticated exploitation, though there is no public exploit identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0-1.11.5 is possible for any authenticated low-privileged user by embedding malicious code in custom components within stored flows. The root cause is a missing server-side authorization check (CWE-862) - the platform executes custom Python component logic without verifying whether the caller has sufficient privileges to run arbitrary code, not a failure to authenticate them. IBM has released a patch via support advisory 7286666; no public exploit or CISA KEV listing has been identified at time of analysis.
Authenticated non-administrative users in IBM Langflow OSS 1.0.0-1.11.5 can execute arbitrary OS commands at the application process privilege level by constructing a flow that uses an MCP Tools component configured with a local stdio subprocess transport. This attack path explicitly circumvents both the LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY and LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS server-side enforcement controls - meaning deployments that relied on these flags for protection are not protected against this specific vector. Full exploitation enables credential theft from the process environment, file system tampering, and lateral movement to backend services reachable from the server. No public exploit or CISA KEV listing has been identified at time of analysis, but the low entry bar (any authenticated account) makes this a high-priority patch for multi-tenant or shared Langflow deployments.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.11.5 allows unauthenticated remote attackers to coerce the application server into fetching arbitrary internal network resources by supplying malicious URLs to the platform's URL-processing functionality. The scope-changed CVSS vector (S:C/C:H) reflects that exploitation exposes systems beyond Langflow itself - including cloud metadata services, internal APIs, and private network hosts accessible from the Langflow host. No public exploit has been identified at time of analysis; a vendor patch is available via IBM's support portal.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.11.5 allows unauthenticated remote attackers to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal network services, cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), and other resources inaccessible to the attacker directly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H) confirms this requires no authentication and trivial network access, with high confidentiality impact. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Persistent API key access in IBM Langflow OSS 1.0.0-1.11.5 allows authenticated remote attackers to continue executing AI workflows and extracting sensitive data even after their user accounts have been deactivated. The vulnerability stems from insufficient session expiration (CWE-613): API keys issued to users are not invalidated when those accounts are disabled, leaving a persistent backdoor for former users or compromised credentials. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS reflects High confidentiality and High integrity impact, driven by the ability to both execute flows and access sensitive pipeline data.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows any authenticated low-privileged user to inject and execute arbitrary server-side code by embedding special characters in flow display names. The root cause is inadequate neutralization of user-controlled input before it enters a code-generation or evaluation context (CWE-94), yielding full host compromise across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in IBM Langflow OSS (versions 1.0.0 through 1.10.3) enables a remote authenticated attacker to escape restricted directory boundaries and execute arbitrary code on the server. The flaw (CWE-22) is present in IBM's enterprise packaging of the Langflow AI workflow platform and is network-exploitable with low-privilege credentials, yielding full C:H/I:H/A:H impact per CVSS 8.8. A vendor patch is available via IBM's security advisory; no public exploit code has been identified at time of analysis.
Improper authorization (IDOR/CWE-639) in IBM Langflow OSS 1.0.0 through 1.10.2 allows a remote authenticated attacker to access other users' workflow data and inject messages into workflow history they do not own. The flaw stems from user-controlled keys not being validated against the authenticated session's authorization scope, enabling horizontal privilege escalation across tenant workflows. No public exploit or active exploitation has been identified; IBM has released a patch and the SSVC assessment confirms exploitation is currently none with partial technical impact.
Unauthenticated remote information disclosure in IBM Langflow OSS 1.0.0 through 1.11.2 allows network-accessible attackers to retrieve sensitive credential fields that are incompletely scrubbed from API responses or workflow data outputs. The CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H) confirms this is exploitable over the network without any authentication or user interaction, and the high confidentiality impact reflects that leaked credentials may include API keys, passwords, or tokens used to integrate with downstream services. No public exploit code or active exploitation has been identified at time of analysis, and IBM has released a patch via their security advisory.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.11.2 enables authenticated remote attackers to exploit a URL parser discrepancy, causing the application to issue unauthorized backend requests to internal services and expose sensitive information beyond the application's trust boundary. The CVSS scope-change metric (S:C) confirms that impact extends past the Langflow instance itself to internal network resources not directly reachable by the attacker. Vendor patch is available via IBM's support portal; no public exploit code or active exploitation has been identified at time of analysis.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.11.2 allows unauthenticated remote attackers to induce the server to issue HTTP requests to attacker-controlled destinations, enabling exfiltration of sensitive information from internal network resources, cloud metadata endpoints, or the application's own environment. The CVSS vector (PR:N/AV:N/AC:L) indicates this is exploitable without authentication at low complexity, which is notable for an AI workflow platform likely deployed with access to cloud infrastructure credentials. No public exploit code or active exploitation has been identified at time of analysis, though the automatable SSVC signal and high confidentiality impact make this a meaningful exposure in cloud-hosted or hybrid deployments.
Authenticated path traversal in IBM Langflow OSS 1.0.0 through 1.11.2 allows any logged-in user to read arbitrary files from the server filesystem - including JWT signing keys, the application secret_key, the runtime database, /proc/self/environ, and other tenants' uploaded files - by supplying absolute paths or traversal sequences in the files parameter of a build request. What elevates the risk beyond a standard directory traversal is the exfiltration mechanism: file contents are embedded directly into the LLM prompt and transmitted to the configured model endpoint, meaning secrets leave the controlled environment and reach third-party AI provider infrastructure. This attack path bypasses the LANGFLOW_RESTRICT_LOCAL_FILE_ACCESS=true containment flag, which enforces restrictions on other file-reading components but was never applied to the Chat Input to Message attachment pipeline. No public exploit code has been identified at time of analysis.
Authenticated command injection in IBM Langflow OSS 1.0.0 through 1.11.1 lets any logged-in flow user escalate to arbitrary OS command execution under the server process identity. By saving a flow containing a crafted 'type' field and triggering a build of a wrapper flow that references it, the attacker coerces the backend into evaluating attacker-controlled code, defeating the LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false guardrail intended to block custom code execution. The vendor (IBM) reported it and has released a fix; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.1 arises from the A2A (agent-to-agent) public endpoint failing to properly enforce security restrictions, letting a network attacker inject and run arbitrary code on the host. The CWE-94 code-injection flaw carries a critical 9.8 CVSS score with a network, no-privilege, no-interaction vector, meaning any reachable instance is directly at risk. IBM has released a fix; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Namespace collision between user identifiers in IBM Langflow OSS 1.0.0 through 1.11.1 exposes sensitive information and enables unauthorized message injection by unauthenticated remote attackers. The flaw, rooted in CWE-639 (authorization bypass via user-controlled key), allows an attacker to resolve or collide with another user's namespace without requiring authentication, as confirmed by the CVSS vector (PR:N). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, network-accessible attack surface warrants prompt remediation.
Path traversal in IBM Langflow OSS 1.0.0 through 1.11.1 exposes arbitrary server-side files to unauthenticated remote attackers over the network. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms low-complexity exploitation requiring no credentials or user interaction, with high confidentiality impact limited to file reads - no write or availability impact. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis, but the unauthenticated network vector and low attack complexity make internet-facing instances a realistic opportunistic target once details circulate.
Remote unauthenticated execution of arbitrary AI workflows in IBM Langflow OSS 1.0.0 through 1.11.1 exposes sensitive information via an authentication bypass (CWE-287). The CVSS 3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) confirms zero prerequisites - any network-reachable instance can be targeted without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the trivial attack complexity combined with high confidentiality impact and vendor-confirmed patch availability makes this an immediate remediation priority for any organization running an exposed Langflow instance.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.1 allows a network-accessible authenticated attacker with low privileges to inject and execute arbitrary code server-side due to improper control of code generation (CWE-94). The CVSS 8.8 High score reflects low attack complexity, no required user interaction, and full confidentiality, integrity, and availability impact against the vulnerable host. IBM has released a patch; no public exploit or CISA KEV listing is identified at time of analysis.
Unauthenticated remote attackers can overwrite administrator email addresses and abuse IBM Langflow OSS as an outbound mail relay by exploiting a missing authentication control on the registration endpoint, affecting versions 1.0.0 through 1.10.0. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms trivially reachable exploitation with no credentials or user interaction required. No public exploit or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes this viable for opportunistic exploitation once the endpoint is discovered.
Account takeover in IBM Langflow OSS versions 1.0.0 through 1.9.6 is possible because the platform fails to limit repeated failed authentication attempts (CWE-307), letting remote attackers brute-force or credential-stuff their way into user accounts. IBM (the reporting vendor) rates it CVSS 9.1 with high confidentiality and integrity impact, reflecting full compromise of a targeted account. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the missing lockout control is trivial to abuse against weak or reused credentials.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by any authenticated attacker due to improper validation of module imports, classified under CWE-94 (Code Injection). The CVSS 8.8 score reflects full confidentiality, integrity, and availability impact with no user interaction required beyond low-privilege authentication. No public exploit code has been identified at time of analysis, EPSS sits at 0.34% (27th percentile), and SSVC designates exploitation as 'none' currently - though the SSVC technical impact is rated 'total', confirming the severity of successful exploitation.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by remote attackers holding low-privilege credentials via server-side code injection (CWE-94). The CVSS score of 8.8 reflects full confidentiality, integrity, and availability impact with a low-complexity network attack path requiring only valid user authentication. No public exploitation has been confirmed - EPSS places the exploitation probability at 0.36% (29th percentile) and SSVC rates exploitation status as none and the attack as non-automatable, though SSVC's technical impact rating is total, consistent with arbitrary code execution.
Remote code execution in IBM Langflow OSS 1.0.0-1.10.3 allows authenticated remote attackers to inject and execute arbitrary Python code by crafting payloads that evade the platform's AST-based security scanning mechanism. The flaw (CWE-94, Code Injection) is particularly insidious because the defensive AST validation layer gives a false sense of protection while silently passing malicious constructs to the Python runtime. No public exploit or CISA KEV listing exists at time of analysis, but the low-complexity, fully network-accessible attack path with complete confidentiality, integrity, and availability impact warrants urgent patching - especially for any internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0-1.10.3 allows authenticated low-privilege users to trigger arbitrary Python execution on the backend server by submitting crafted Agentic Assistant workflows containing malicious LLM-generated components that are evaluated server-side during validation before user approval is granted. The flaw (CWE-94, Code Injection) arises because the validation pipeline eagerly executes model-generated Python without sandboxing or deferral, giving attackers backend process-level privileges to exfiltrate data, interact with the file system, or initiate outbound network connections. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS places exploitation probability at 0.22% (13th percentile), but SSVC rates technical impact as total, making this a high-priority patch target for multi-user or internet-exposed deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 allows any internet-reachable attacker to execute arbitrary server-side code using only two HTTP requests. The vulnerability is rooted in CWE-94 (Code Injection), enabling full server compromise with no user interaction. A vendor patch is available via IBM advisory, and no public exploit has been identified at time of analysis - however the trivially low attack complexity makes any internet-exposed instance an immediate remediation priority.
Remote code execution in IBM Langflow OSS (versions 1.0.0 through 1.10.3) allows authenticated attackers to execute arbitrary Python code by exploiting a cryptographic weakness (CWE-326) in the custom component validation mechanism. When the optional hardening mode is enabled - the feature intended to restrict execution to trusted component templates - the application validates submitted component code against a truncated SHA-256 digest, making it computationally feasible for an attacker to craft a malicious Python file that collides with a trusted template's hash and bypasses the validation gate entirely. No public exploit code has been identified at time of analysis; a vendor patch is available per IBM advisory, though the exact fixed version is not stated in available data.
Remote code injection in IBM Langflow OSS 1.0.0 through 1.10.3 allows an authenticated remote attacker to execute arbitrary code on the underlying server by supplying malicious input through user-controlled code fields within the platform. The CVSS vector (AV:N/AC:L/PR:L) confirms the attack is network-reachable at low complexity, requiring only low-privilege credentials, with full confidentiality, integrity, and availability impact on the host. A vendor patch is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Path traversal in IBM Langflow OSS versions 1.0.0 through 1.10.3 enables authenticated remote attackers to read arbitrary files on the underlying system by submitting URLs containing dot-dot sequences (/../). The CVSS scope change metric (S:C) confirms that exploitation reaches beyond the application's own directory boundary, exposing system-level files such as credentials, configuration, or private keys to any low-privileged account holder. No public exploit code has been identified at time of analysis, though IBM has released a patch via advisory node/7282647.
Cross-user chat history disclosure in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to read other users' conversation history by exploiting session_id collision in the MemoryComponent. The MemoryComponent.retrieve_messages and store_message methods validate only session_id when filtering records, omitting flow_id and user_id ownership checks, which exposes multiple REST API endpoints to unauthorized cross-user data access. No public exploit has been identified at time of analysis, but the straightforward exploitation path and High confidentiality impact make this a genuine remediation priority for any multi-user Langflow deployment.
Broken access control in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to inject arbitrary graph data into the shared execution cache for flows they do not own, via the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. The endpoint performs no ownership validation, enabling cross-user cache pollution that can corrupt other users' workflow state, trigger unauthorized execution of foreign flows, or produce denial of service across a shared platform instance. No public exploit code exists and CISA KEV does not list this vulnerability; EPSS (0.20%, 10th percentile) and SSVC (exploitation: none, automatable: no) collectively indicate low immediate exploitation risk despite the high CVSS score.
Predictable Fernet encryption keys in IBM Langflow OSS 1.0.0 through 1.10.3 allow attackers to decrypt stored API keys and authentication tokens, because when a user secret is shorter than 32 characters the platform derives keys with Python's non-cryptographic `random` (Mersenne Twister) module. Because the Mersenne Twister PRNG is deterministic, identical seeds reproduce identical keys, so an adversary who can reconstruct the seeding conditions can regenerate the key and read every secret Langflow encrypted with it. No public exploit identified at time of analysis; EPSS is low (0.11%) and CISA SSVC records no known exploitation.
Predictable Fernet encryption key generation in IBM Langflow OSS (versions 1.0.0 through 1.10.3) stems from the ensure_fernet_key() function deriving keys from a cryptographically weak source (CWE-338), letting an attacker reconstruct the symmetric key that protects stored secrets such as API keys, credentials, and connection variables. Because the key is guessable rather than random, an actor who can read Langflow's encrypted data store can decrypt it and, depending on how the key is reused, potentially forge or tamper with protected values. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), but IBM rates the flaw CVSS 9.8 and a vendor patch is available.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.10.3 enables authenticated low-privilege users to coerce the application server into issuing arbitrary outbound HTTP requests against internal infrastructure. The root cause is unsanitized pass-through of the OLLAMA_BASE_URL parameter directly into requests.get() inside validate_model_provider_key(), with no scheme enforcement, host allowlisting, or private-range (loopback, RFC1918, link-local) filtering. No active exploitation confirmed (not in CISA KEV), but the network-accessible, low-complexity attack path and high confidentiality impact (C:H) make this a meaningful internal-network pivot risk for organizations running Langflow with AI provider integration enabled.
OS command injection in IBM Langflow OSS 1.0.0 through 1.10.3 enables remote authenticated attackers to execute arbitrary system commands on the underlying server. The flaw stems from insufficient sanitization of user-supplied input passed to OS-level command execution routines (CWE-78), granting full system-level access with a single authenticated request. No public exploit code has been identified at time of analysis, and CISA does not list this in KEV, though CVSS-assessed technical impact is total across confidentiality, integrity, and availability.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.10.3 is reachable by any authenticated low-privileged user who can modify MCP server configurations. Improper validation of the command field in those configurations allows injected shell commands to be executed with the application's process privileges, yielding full confidentiality, integrity, and availability impact. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, network-accessible attack path against a growing AI-tooling platform warrants prompt patching.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 allows authenticated remote attackers to run arbitrary commands by supplying crafted configuration parameters that bypass the application's incomplete input denylist (CWE-184). The flaw carries a CVSS 8.8 score with full confidentiality, integrity, and availability impact, and SSVC rates the technical impact as total. No active exploitation is confirmed - EPSS sits at 0.42% (35th percentile) and the vulnerability is absent from CISA KEV - though the low attack complexity makes it a genuine priority for any internet-exposed Langflow deployment with untrusted authenticated users.
Host filesystem read and write access in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by any authenticated low-privilege user via insufficient filtering of Docker volume-mount and device-mapping arguments passed to Docker-based MCP servers. By injecting unsanitized flags such as --volume into MCP server configuration, an attacker can bind-mount arbitrary host directories into a spawned container, exposing or tampering with sensitive files outside the intended Docker isolation boundary. No public exploit code has been identified at time of analysis and no CISA KEV listing exists, but the network-exploitable, low-complexity attack path and full CIA impact score (CVSS 8.8) make this a high-priority patch target for any organization running Langflow in Docker environments with externally accessible or multi-tenant access.
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.3 exposes the Model Context Protocol (MCP) composer endpoint to unauthenticated remote access when projects are configured with auth_type=oauth and MCP composer is enabled - which is the default deployment state. An unauthenticated network attacker can reach the MCP composer endpoint and read confidential project data (C:H) without supplying valid credentials, entirely bypassing the OAuth authentication gate. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vendor (IBM) has confirmed the issue and released a patch.
Remote authenticated attackers can bypass localhost-only access restrictions in IBM Langflow OSS 1.0.0 through 1.10.3 to write arbitrary MCP (Model Context Protocol) server configurations to IDE configuration files on the underlying host system. The CVSS scope change (S:C) confirms this escapes the Langflow application boundary, enabling persistent manipulation of developer IDE environments on the host. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is available.
Remote code injection in IBM Langflow OSS versions 1.0.0 through 1.10.0 allows an authenticated remote attacker to execute arbitrary code on the underlying host by supplying malicious user-controlled code that is improperly validated (CWE-94). Because Langflow evaluates user-supplied code as part of its low-code AI/agent flow-building functionality, exploitation grants full compromise of the server hosting the application. There is no public exploit identified at time of analysis, but the CVSS 3.1 base score of 9.9 with a scope change reflects that a successful attack can break out of the application context to affect other system components.
Cross-tenant vector document disclosure in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privilege user read another user's private Chroma-backed documents by building a flow that reuses the victim's persist_directory and collection_name, returning exact victim content in the attacker's workflow output. The same shared-namespace flaw also lets the attacker write their own documents into the victim's collection, corrupting its integrity. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as none, but the CVSS 8.1 rating reflects the combined high confidentiality and integrity impact.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.1 stems from improper input validation in the PythonREPL sandbox, allowing a low-privileged authenticated user to escape the sandbox and run arbitrary Python. Because the flaw carries a scope-changing CVSS 3.1 score of 9.9 (S:C, C/I/A all High), a successful exploit can compromise the underlying host beyond the intended sandbox boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Arbitrary file read in IBM Langflow OSS versions 1.0.0 through 1.10.1 allows remote unauthenticated attackers to retrieve files outside the intended web root by submitting URLs containing directory-traversal ("../") sequences. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, exploitation needs no authentication or user interaction and can expose sensitive files such as configuration, secrets, or source code. No public exploit identified at time of analysis, and there is no indication of active exploitation.
Broken object-level authorization in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privileged user read and tamper with build jobs belonging to other users by abusing improper access control on log-retrieval and unauthenticated build endpoints. Because Langflow orchestrates LLM/agent workflow builds, a cross-tenant attacker can view sensitive build logs (high confidentiality impact) and interfere with others' jobs (limited availability impact). A vendor patch is available; there is no public exploit identified at time of analysis and the flaw is not on CISA KEV.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.1 allows remote attackers to run arbitrary OS commands by injecting shell-control environment variables into the MCP (Model Context Protocol) stdio launcher. The DANGEROUS_ENV_VARS blocklist in src/lfx/src/lfx/base/mcp/util.py omits SHELLOPTS, BASHOPTS, and PS4, letting an attacker abuse Bash's xtrace behavior to execute commands when a stdio-based MCP server subprocess is spawned. Rated CVSS 9.8 with a network, no-privilege, no-interaction vector; a vendor patch is available, but no public exploit code or CISA KEV listing has been identified at the time of analysis.
Cross-user information disclosure in IBM Langflow OSS 1.0.0-1.10.1 allows authenticated attackers to access private vector content and poison query results by reusing another user's FAISS namespace. This leads to high confidentiality impact and low integrity impact; the vulnerability has a CVSS 3.1 score of 7.1, and a vendor patch is available.
Cross-user file access in IBM Langflow OSS (1.0.0 through 1.10.1) lets an authenticated user abuse the SaveToFile component to read and modify files uploaded by other users by supplying absolute paths that point into victim storage locations. Append mode enables exfiltration of victim data into the attacker's namespace (confidentiality), while overwrite mode allows replacing victim content with arbitrary data (integrity), collapsing the per-user storage ownership boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available.
Authentication bypass and full data compromise affects IBM Langflow OSS 1.0.0 through 1.10.1, which ships hard-coded credentials (a static password or cryptographic key) embedded in the application. Because the same secret is present in every deployment, remote attackers who read it from the public source or a binary can authenticate to inbound interfaces, impersonate the app to external components, or decrypt internal data on any affected instance. No public exploit identified at time of analysis, but the shared-secret nature makes exploitation trivial once the value is known.
Arbitrary file write in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated user create a malicious flow that points to an attacker-controlled URL returning a crafted Content-Disposition header, causing the Langflow process to write attacker-supplied content to any filesystem path it can access. Because writes can land on startup scripts, keys, or configuration files, this path-traversal (CWE-22) flaw is a realistic route to full server compromise. IBM has released a fix; no public exploit identified at time of analysis and the CVE is not in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows an authenticated remote attacker to run arbitrary code because validation is not fully enforced on Model Context Protocol (MCP) server configuration files, permitting injection of attacker-controlled commands or server definitions. IBM has published a fix advisory (node/7278932). With CVSS 8.8 (PR:L), a low-privileged user of the Langflow instance can escalate to full code execution on the host; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Arbitrary file read in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated attacker traverse the filesystem to exfiltrate sensitive files - most critically the JWT signing key - and then forge valid authentication tokens to impersonate any user, including administrators. The path-traversal-to-account-takeover chain turns a low-privilege foothold into full application compromise. No public exploit identified at time of analysis, and the EPSS score is low (0.38%, 31st percentile), but a vendor patch is available and the impact is severe.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows authenticated users to override arbitrary component parameters at runtime through the API, bypassing the parameter filtering logic in the apply_tweaks() function (CWE-94 code injection). Because a low-privileged authenticated account is sufficient and the impact is full compromise of confidentiality, integrity, and availability (CVSS 8.8), this maps to server-side code execution on the Langflow host. There is no public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows attackers to run arbitrary code by planting a malicious pickle payload that the AsyncDiskCache deserializes with unauthenticated pickle.loads(). Any actor able to influence cached data - via file system access, crafted workflow inputs, custom components, or API manipulation - gains full compromise at the privilege of the Langflow server process. Rated CVSS 9.9 and reported by IBM with a vendor patch available; no public exploit identified at time of analysis.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 lets any logged-in user run arbitrary Python — and therefore arbitrary OS commands — with the privileges of the Langflow server process. The flaw is a design failure in the POST /api/v1/validate/code endpoint, which passes user-supplied code straight into Python's exec() with no sandbox, validation, or privilege drop. Rated CVSS 9.9 by IBM; no public exploit identified at time of analysis, though the trivial exec()-based trigger makes exploitation straightforward once authenticated.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 stems from broken webhook authentication that skips API key validation whenever WEBHOOK_AUTH_ENABLE is False - which is the shipped default. Any remote attacker who learns a flow's UUID can invoke that flow's webhook endpoint as though they were its owner, running arbitrary flow logic and reaching RCE. No public exploit identified at time of analysis, but the CVSS 9.8 rating and default-vulnerable configuration make this a high-priority patch.
Privilege escalation to remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows an authenticated user to elevate their account to superuser by directly manipulating the underlying database, then execute arbitrary system commands and achieve full compromise of the host running the Langflow service. The flaw (CWE-94, code injection) carries a critical CVSS 9.9 with a scope change, meaning code runs with the Langflow service account's permissions beyond the vulnerable component. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but a vendor patch is available.
Arbitrary file write in IBM Langflow OSS 1.0.0 through 1.10.0 lets an attacker who controls an external HTTP server plant files at attacker-chosen paths on the Langflow host. The flaw lives in the APIRequest component's 'Save to File' feature, which trusts filenames from a response Content-Disposition header without sanitizing path traversal sequences, so a malicious server response can escape the temporary directory and write to any location the Langflow process can reach. No public exploit identified at time of analysis, and it is not in CISA KEV; a patch is available per IBM's advisory.
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.0 lets an unauthenticated remote attacker retrieve a long-lived superuser bearer token from the /api/v1/login/auto_login endpoint whenever the AUTO_LOGIN setting is on - which is the default. Because the endpoint mints full-admin tokens with no credentials, any network-reachable attacker gains complete administrative control, and overly permissive CORS can leak those tokens to unintended origins. A vendor patch is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0 through 1.10.0 (Langflow versions up to 1.9.2) allows authenticated users with flow-creation privileges to bypass the allow_custom_components=false control via the Policies component's ToolGuard integration. Because validation only inspects the main component code and ignores dynamic CodeInput fields, attackers persist malicious Python in a flow that runs server-side when a guarded tool executes. No public exploit has been identified at time of analysis, but the flaw is IBM-confirmed with a vendor patch and carries a critical 9.9 CVSS due to cross-tenant escalation through the agentic MCP update_flow_component_field tool.
Unauthenticated remote code execution in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets any network-reachable attacker achieve full RCE on default deployments by chaining two endpoints: /api/v1/auto_login, which mints SUPERUSER tokens to any caller, and /api/v1/validate/code, which passes user-supplied code to Python's exec(). CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N) and a vendor patch is available; there is no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Missing authentication in IBM Langflow OSS 1.0.0 through 1.10.0 lets unauthenticated remote attackers register unlimited user accounts against any exposed instance. When the documented NEW_USER_IS_ACTIVE=true option is set, those accounts become immediately active and can log in to reach known remote-code-execution endpoints, providing a full authentication foothold without relying on AUTO_LOGIN. No public exploit identified at time of analysis, but the CVSS 9.8 rating and unauthenticated network vector make internet-facing deployments a high priority.
Improper authorization enforcement in IBM Langflow OSS 1.0.0 through 1.9.6 lets unauthenticated remote attackers reach protected MCP (Model Context Protocol) project resources and invoke MCP operations through the Streamable MCP transport endpoint. Because the flaw bypasses authentication entirely on a network-facing endpoint and is rated CVSS 9.8 with full confidentiality, integrity, and availability impact, any exposed Langflow instance is at risk. There is no public exploit identified at time of analysis, and the EPSS probability is low (0.24%, 15th percentile), indicating exploitation has not yet become widespread.
Arbitrary code execution in IBM Langflow OSS versions 1.0.0 through 1.10.0 allows remote attackers to run code on the host by submitting flow definitions containing nodes with missing or empty component type fields. The improper input validation (CWE-20) lets malformed node specifications bypass type checks and reach unsafe execution paths in the low-code AI workflow engine. The CVSS vector (AV:N/PR:N) indicates network-reachable, pre-authentication exploitation; no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Insecure deserialization (CWE-502) in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets any party with access to the backing Redis store inject a malicious serialized object that Langflow deserializes, yielding arbitrary code execution with full application privileges. Successful exploitation exposes all stored secrets, flow data, and the underlying host, effectively a complete compromise of the Langflow instance. No public exploit has been identified at time of analysis, and the issue is not listed in CISA KEV; a vendor patch is available per IBM advisory node 7278443.
Code injection in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets an authenticated user execute arbitrary operating-system commands and read sensitive files such as stored credentials, escalating from low-privileged application access to full host compromise. Rated CVSS 9.9 with a scope-changing vector, the flaw enables lateral movement once an attacker holds any valid Langflow account. No public exploit identified at time of analysis, but a vendor patch is available.
Credential disclosure in IBM Langflow OSS versions 1.0.0 through 1.10.0 stems from a weak, reversible key-derivation mechanism used to protect secrets encrypted at rest, allowing an attacker who can reach the stored credential data to recover the encryption key and decrypt every stored credential. Because Langflow stores API keys, database connection strings, and third-party service tokens used by AI workflow components, recovery of these secrets gives an attacker the keys to all integrated systems. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score supplied, so the threat is currently theoretical but high-impact, and IBM (the reporter) has released a fix.
Authorization bypass in IBM Langflow OSS 1.0.0 through 1.8.4 allows unauthenticated remote attackers to access protected Model Context Protocol (MCP) project resources and invoke MCP operations through the Streamable MCP transport endpoint. The CVSS 9.8 rating reflects unauthenticated network exploitation with full confidentiality, integrity, and availability impact, though no public exploit identified at time of analysis and the flaw is not currently listed in CISA KEV.
Authenticated remote code execution affects IBM Langflow OSS 1.0.0 through 1.12.2, where improper control of code generation lets any account with at least low privileges (CVSS PR:L, AV:N, UI:N) cause attacker-supplied code to run server-side on the Langflow host, yielding high confidentiality, integrity, and availability impact (CVSS 8.8). Exploitation is not possible against a default install without valid credentials, and no public exploit code or confirmed active exploitation was identified at time of analysis. The practical exposure therefore concentrates on internet-reachable or multi-tenant instances that permit self-registration or host untrusted users; isolated, single-tenant, network-restricted deployments with trusted operators carry substantially lower risk.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.2 lets any remote user holding a valid low-privileged account execute arbitrary code on the hosting server, with high impact to confidentiality, integrity, and availability (CVSS 8.8, PR:L, no user interaction required). The attack surface is the code path where special elements used in code are not properly neutralized (CWE-94), so deployments that allow untrusted or self-registered accounts to author and run flows are the most exposed, while instances with closed registration and no internet exposure are materially less at risk. No public exploit code has been identified at time of analysis, EPSS is only 0.58% (46th percentile), and CISA SSVC rates exploitation as 'none', making this a serious-but-not-emergency issue; a vendor patch is available per IBM's advisory.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows a low-privileged user to run arbitrary code because the platform improperly controls generation of executable code (CWE-94). Exploitation requires only a valid account on the instance (CVSS PR:L, AV:N, AC:L, UI:N), so an attacker who holds or obtains any credential able to create, import, or execute a flow/component that reaches the vulnerable code-generation path can achieve full confidentiality, integrity, and availability impact on the host. No public exploit code was identified at time of analysis, CISA's SSVC assessment records exploitation as "none", and EPSS is 0.58% (46th percentile), placing this as a genuinely serious but not emergency-tier issue whose real-world risk scales with how exposed the Langflow instance is and how freely low-privilege accounts are provisioned.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker with flow-authoring privileges to inject and execute arbitrary code through Langflow's code-generation mechanism (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as high severity (8.8), requiring network reachability, low privileges, and no user interaction; however, in typical deployments where flow creation or modification is broadly granted, the practical barrier may be lower than the PR:L metric implies. No public exploit code or CISA KEV entry has been identified at time of analysis, and EPSS is 0.61% (48th percentile); IBM has released a vendor patch.
Deserialization of untrusted cache data in IBM Langflow OSS 1.0.0 through 1.12.2 can execute attacker-controlled code with the privileges of the Langflow service process, but only for an attacker who has already obtained two things: the Langflow server secret and write access to the backing Redis instance used as the application cache. Because both prerequisites are effectively gated - the server secret is a trusted signing/trust value and Redis is normally bound to localhost or a private, authenticated network - this is not exploitable by an anonymous remote attacker against a default deployment, which is why the practical risk is lower than the 7.5 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Remote code execution can result in IBM Langflow OSS 1.0.0 through 1.12.2 through a dependency confusion weakness, where the product resolves an expected dependency from a public package registry instead of the intended trusted source. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates an unauthenticated remote attacker with no user interaction required, and the unpatched severity is rated 9.8; however, our independent assessment lowers the attack complexity to AC:H because successful exploitation depends on the attacker knowing or guessing the exact dependency name and on the victim's resolver preferring an attacker-published public package over the legitimate one, typically during an install, build, or import event rather than against a running service. There is no confirmed active exploitation (CISA KEV does not list this CVE), SSVC records Exploitation: none and Automatable: no, no public exploit code has been identified at time of analysis, and EPSS is only 0.68% (51st percentile), so the practical near-term risk is materially lower than the 9.8 headline suggests. A vendor patch is available per the IBM advisory.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, low-privilege authenticated attacker to retrieve objects belonging to other users by manipulating a user-controlled identifier that the application fails to scope to the requesting principal (CWE-639, IDOR-style authorization bypass). The flaw is network-reachable with low attack complexity and no user interaction, but it is gated on the attacker already holding valid credentials for a low-privilege account (CVSS PR:L); the assessed impact is a high-confidentiality, read-only exposure with no demonstrated integrity or availability effect, so realistic risk concentrates in multi-user or multi-tenant Langflow deployments where a low-trust account can reach another tenant's or user's data. Patch available per vendor advisory (IBM support node 7290694); no public exploit identified at time of analysis.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any attacker who can reach the service execute arbitrary operating system commands on the underlying host. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw requires no credentials, no user interaction, and no non-default configuration, so a default Langflow deployment exposed beyond localhost is directly exploitable. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); IBM has published a vendor advisory with a fix, and practical risk is concentrated in self-hosted developer instances that are bound to reachable interfaces rather than being restricted to localhost or placed behind authentication and firewalling.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who already holds a valid low-privilege session execute arbitrary code on the host by sending a crafted request that bypasses improper input validation. The flaw is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8), so the authentication requirement is the main barrier; deployments with open or self-service sign-up, internet exposure, or multi-tenant use carry the highest risk. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any holder of valid credentials - even a low-privileged one - submit or edit a flow that reaches the server-side code-generation and execution path, resulting in arbitrary OS command execution on the Langflow backend. IBM scores it 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and classifies the root cause as CWE-94 code injection; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so active exploitation is not confirmed. The decisive risk factor is deployment posture: internet-exposed or multi-tenant instances running with authentication disabled, default or shared credentials, or open self-registration collapse the PR:L barrier and behave like unauthenticated RCE targets.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any user who can log in to the instance run arbitrary code on the host, because the platform fails to properly constrain attacker-supplied input before it reaches a code-execution path. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning low-complexity, network-reachable exploitation that requires only a low-privileged account but yields full confidentiality, integrity, and availability impact - no user interaction and no elevated privileges are needed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, but IBM has published a vendor advisory with a fix, so the practical exposure is greatest for organizations that expose Langflow to untrusted networks or provision accounts broadly.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker to run arbitrary operating-system commands by supplying crafted input to a component that fails to neutralize special elements before passing them to an OS command or code-evaluation path (CWE-94). Per the assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires a valid low-privilege authenticated session on the Langflow instance, needs no victim interaction, and yields full confidentiality, integrity, and availability impact on the affected host. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the practical risk is concentrated on network-exposed Langflow servers that use weak, shared, or default credentials, since a compromised or low-privilege account is the only prerequisite.
Improper access control in the vertex result caching subsystem of IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote authenticated attacker read sensitive cached data or inject malicious content into vertex results that other users then consume. The issue carries a CVSS 3.1 base score of 8.3 (High) under the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, meaning it is network-reachable with low complexity and requires only a low-privileged account, while yielding high confidentiality and integrity impact and low availability impact. No public exploit code has been identified at time of analysis and the flaw does not appear in CISA KEV; IBM has published a patch advisory (node/7290694), so exposure is limited to unpatched deployments and to attackers who already hold valid credentials on the instance.
Authenticated remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where an incomplete blocklist in the built-in code security scanner can be bypassed to execute arbitrary code on the server. Exploitation requires a valid low-privilege account (CVSS PR:L) and the ability to submit code evaluated by the scanner; unauthenticated attackers are not sufficient. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the high CVSS base score of 8.8 and the multi-tenant exposure of typical Langflow deployments make the risk significant where untrusted users can register or be provisioned.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets an authenticated attacker escape the application's code execution sandbox and run arbitrary commands on the host. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) confirms network reachability and a low-privileged authenticated session as the only precondition, with no user interaction required. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the low complexity and high impact make this a genuine prioritization concern for internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows attackers to execute arbitrary code via improper control of code generation (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates remote, unauthenticated, low-complexity exploitation with full confidentiality, integrity, and availability impact, though the independent assessment notes the pre-auth condition is not independently confirmed by the description. A vendor patch is available, and no public exploit code has been identified at time of analysis; risk is highest for internet-exposed instances within the affected version range.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.11.5 is achievable by authenticated users who can submit custom component source code to the platform. The built-in static security scanner contains a logic error (CWE-693: Protection Mechanism Failure) in its alias-tracking path: when a dangerous callable is referenced indirectly through an annotated class-body assignment, the resolved callable is never validated against the blocklist, making the scan trivially bypassable with a crafted construct. If the malicious component reaches runtime execution, OS commands run in-process with the full privileges of the Langflow service account. No public exploit has been identified at time of analysis, but IBM has released a patch and the network-accessible, low-privilege attack surface makes this a meaningful risk in any multi-user or shared Langflow deployment.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows a low-privilege attacker to execute arbitrary OS commands by submitting crafted input that bypasses the platform's security scanner denylist. The root cause is an incomplete denylist (CWE-78) in the scanner responsible for gatekeeping executable content within AI workflow components - meaning certain command injection payloads are not intercepted and reach the underlying OS. No public exploit has been identified at time of analysis, though the authenticated-only barrier is a relatively low bar in multi-tenant or shared Langflow deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows authenticated network attackers to run arbitrary operating system commands by supplying crafted input to an unguarded eval() call within the application. The root cause is CWE-94 code injection - attacker-controlled data is passed directly to a dynamic evaluation function without sanitization or sandboxing. IBM has released a patch and no public exploit code or CISA KEV listing has been identified at time of analysis, but the straightforward nature of eval()-based injection and the low privilege bar (any authenticated user) make this a meaningful post-authentication escalation risk.
Authenticated remote code execution in IBM Langflow OSS 1.0.0-1.11.5 allows a low-privileged attacker to execute arbitrary OS commands by supplying malicious command-line arguments through the MCP stdio server configuration interface. The root cause (CWE-78: OS Command Injection) is insufficient sanitization of user-controlled argument strings before they are passed to a subprocess invocation, giving the attacker OS-level code execution within the application's security context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the authenticated-but-low-privilege attack path makes this a meaningful threat in multi-tenant or shared Langflow deployments.
Remote OS command execution in IBM Langflow OSS (versions 1.0.0 through 1.11.5) lets remote attackers run arbitrary operating-system commands due to improper neutralization of special elements passed into a shell command (CWE-78). Per the CVSS vector (PR:N/UI:N), exploitation requires no authentication or user interaction and yields full confidentiality, integrity, and availability impact on the host. No public exploit has been identified at time of analysis, though the vendor has released a patch.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows authenticated low-privileged users to execute arbitrary server-side code by exploiting an incomplete environment variable blocklist. The root cause (CWE-94, Code Injection) means the platform's intended restrictions on environment variable access can be circumvented by supplying references to variables omitted from the blocklist, resulting in full confidentiality, integrity, and availability compromise. No public exploit has been identified at time of analysis, and a vendor-released patch is available per IBM advisory node/7286666.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows an unauthenticated remote attacker to run arbitrary code by injecting malicious code that is evaluated during graph construction (CWE-94). Because Langflow is a visual framework for building LLM/agent workflows whose flows are assembled into executable graphs, a crafted flow definition submitted to the server is interpreted as code rather than data. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, network-reachable, unauthenticated exploitation, though there is no public exploit identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0-1.11.5 is possible for any authenticated low-privileged user by embedding malicious code in custom components within stored flows. The root cause is a missing server-side authorization check (CWE-862) - the platform executes custom Python component logic without verifying whether the caller has sufficient privileges to run arbitrary code, not a failure to authenticate them. IBM has released a patch via support advisory 7286666; no public exploit or CISA KEV listing has been identified at time of analysis.
Authenticated non-administrative users in IBM Langflow OSS 1.0.0-1.11.5 can execute arbitrary OS commands at the application process privilege level by constructing a flow that uses an MCP Tools component configured with a local stdio subprocess transport. This attack path explicitly circumvents both the LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY and LANGFLOW_BLOCK_CODE_INTERPRETER_COMPONENTS server-side enforcement controls - meaning deployments that relied on these flags for protection are not protected against this specific vector. Full exploitation enables credential theft from the process environment, file system tampering, and lateral movement to backend services reachable from the server. No public exploit or CISA KEV listing has been identified at time of analysis, but the low entry bar (any authenticated account) makes this a high-priority patch for multi-tenant or shared Langflow deployments.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.11.5 allows unauthenticated remote attackers to coerce the application server into fetching arbitrary internal network resources by supplying malicious URLs to the platform's URL-processing functionality. The scope-changed CVSS vector (S:C/C:H) reflects that exploitation exposes systems beyond Langflow itself - including cloud metadata services, internal APIs, and private network hosts accessible from the Langflow host. No public exploit has been identified at time of analysis; a vendor patch is available via IBM's support portal.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.11.5 allows unauthenticated remote attackers to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal network services, cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), and other resources inaccessible to the attacker directly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H) confirms this requires no authentication and trivial network access, with high confidentiality impact. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Persistent API key access in IBM Langflow OSS 1.0.0-1.11.5 allows authenticated remote attackers to continue executing AI workflows and extracting sensitive data even after their user accounts have been deactivated. The vulnerability stems from insufficient session expiration (CWE-613): API keys issued to users are not invalidated when those accounts are disabled, leaving a persistent backdoor for former users or compromised credentials. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS reflects High confidentiality and High integrity impact, driven by the ability to both execute flows and access sensitive pipeline data.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows any authenticated low-privileged user to inject and execute arbitrary server-side code by embedding special characters in flow display names. The root cause is inadequate neutralization of user-controlled input before it enters a code-generation or evaluation context (CWE-94), yielding full host compromise across confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in IBM Langflow OSS (versions 1.0.0 through 1.10.3) enables a remote authenticated attacker to escape restricted directory boundaries and execute arbitrary code on the server. The flaw (CWE-22) is present in IBM's enterprise packaging of the Langflow AI workflow platform and is network-exploitable with low-privilege credentials, yielding full C:H/I:H/A:H impact per CVSS 8.8. A vendor patch is available via IBM's security advisory; no public exploit code has been identified at time of analysis.
Improper authorization (IDOR/CWE-639) in IBM Langflow OSS 1.0.0 through 1.10.2 allows a remote authenticated attacker to access other users' workflow data and inject messages into workflow history they do not own. The flaw stems from user-controlled keys not being validated against the authenticated session's authorization scope, enabling horizontal privilege escalation across tenant workflows. No public exploit or active exploitation has been identified; IBM has released a patch and the SSVC assessment confirms exploitation is currently none with partial technical impact.
Unauthenticated remote information disclosure in IBM Langflow OSS 1.0.0 through 1.11.2 allows network-accessible attackers to retrieve sensitive credential fields that are incompletely scrubbed from API responses or workflow data outputs. The CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H) confirms this is exploitable over the network without any authentication or user interaction, and the high confidentiality impact reflects that leaked credentials may include API keys, passwords, or tokens used to integrate with downstream services. No public exploit code or active exploitation has been identified at time of analysis, and IBM has released a patch via their security advisory.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.11.2 enables authenticated remote attackers to exploit a URL parser discrepancy, causing the application to issue unauthorized backend requests to internal services and expose sensitive information beyond the application's trust boundary. The CVSS scope-change metric (S:C) confirms that impact extends past the Langflow instance itself to internal network resources not directly reachable by the attacker. Vendor patch is available via IBM's support portal; no public exploit code or active exploitation has been identified at time of analysis.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.11.2 allows unauthenticated remote attackers to induce the server to issue HTTP requests to attacker-controlled destinations, enabling exfiltration of sensitive information from internal network resources, cloud metadata endpoints, or the application's own environment. The CVSS vector (PR:N/AV:N/AC:L) indicates this is exploitable without authentication at low complexity, which is notable for an AI workflow platform likely deployed with access to cloud infrastructure credentials. No public exploit code or active exploitation has been identified at time of analysis, though the automatable SSVC signal and high confidentiality impact make this a meaningful exposure in cloud-hosted or hybrid deployments.
Authenticated path traversal in IBM Langflow OSS 1.0.0 through 1.11.2 allows any logged-in user to read arbitrary files from the server filesystem - including JWT signing keys, the application secret_key, the runtime database, /proc/self/environ, and other tenants' uploaded files - by supplying absolute paths or traversal sequences in the files parameter of a build request. What elevates the risk beyond a standard directory traversal is the exfiltration mechanism: file contents are embedded directly into the LLM prompt and transmitted to the configured model endpoint, meaning secrets leave the controlled environment and reach third-party AI provider infrastructure. This attack path bypasses the LANGFLOW_RESTRICT_LOCAL_FILE_ACCESS=true containment flag, which enforces restrictions on other file-reading components but was never applied to the Chat Input to Message attachment pipeline. No public exploit code has been identified at time of analysis.
Authenticated command injection in IBM Langflow OSS 1.0.0 through 1.11.1 lets any logged-in flow user escalate to arbitrary OS command execution under the server process identity. By saving a flow containing a crafted 'type' field and triggering a build of a wrapper flow that references it, the attacker coerces the backend into evaluating attacker-controlled code, defeating the LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false guardrail intended to block custom code execution. The vendor (IBM) reported it and has released a fix; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.1 arises from the A2A (agent-to-agent) public endpoint failing to properly enforce security restrictions, letting a network attacker inject and run arbitrary code on the host. The CWE-94 code-injection flaw carries a critical 9.8 CVSS score with a network, no-privilege, no-interaction vector, meaning any reachable instance is directly at risk. IBM has released a fix; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Namespace collision between user identifiers in IBM Langflow OSS 1.0.0 through 1.11.1 exposes sensitive information and enables unauthorized message injection by unauthenticated remote attackers. The flaw, rooted in CWE-639 (authorization bypass via user-controlled key), allows an attacker to resolve or collide with another user's namespace without requiring authentication, as confirmed by the CVSS vector (PR:N). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, network-accessible attack surface warrants prompt remediation.
Path traversal in IBM Langflow OSS 1.0.0 through 1.11.1 exposes arbitrary server-side files to unauthenticated remote attackers over the network. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms low-complexity exploitation requiring no credentials or user interaction, with high confidentiality impact limited to file reads - no write or availability impact. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis, but the unauthenticated network vector and low attack complexity make internet-facing instances a realistic opportunistic target once details circulate.
Remote unauthenticated execution of arbitrary AI workflows in IBM Langflow OSS 1.0.0 through 1.11.1 exposes sensitive information via an authentication bypass (CWE-287). The CVSS 3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) confirms zero prerequisites - any network-reachable instance can be targeted without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the trivial attack complexity combined with high confidentiality impact and vendor-confirmed patch availability makes this an immediate remediation priority for any organization running an exposed Langflow instance.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.1 allows a network-accessible authenticated attacker with low privileges to inject and execute arbitrary code server-side due to improper control of code generation (CWE-94). The CVSS 8.8 High score reflects low attack complexity, no required user interaction, and full confidentiality, integrity, and availability impact against the vulnerable host. IBM has released a patch; no public exploit or CISA KEV listing is identified at time of analysis.
Unauthenticated remote attackers can overwrite administrator email addresses and abuse IBM Langflow OSS as an outbound mail relay by exploiting a missing authentication control on the registration endpoint, affecting versions 1.0.0 through 1.10.0. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms trivially reachable exploitation with no credentials or user interaction required. No public exploit or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes this viable for opportunistic exploitation once the endpoint is discovered.
Account takeover in IBM Langflow OSS versions 1.0.0 through 1.9.6 is possible because the platform fails to limit repeated failed authentication attempts (CWE-307), letting remote attackers brute-force or credential-stuff their way into user accounts. IBM (the reporting vendor) rates it CVSS 9.1 with high confidentiality and integrity impact, reflecting full compromise of a targeted account. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the missing lockout control is trivial to abuse against weak or reused credentials.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by any authenticated attacker due to improper validation of module imports, classified under CWE-94 (Code Injection). The CVSS 8.8 score reflects full confidentiality, integrity, and availability impact with no user interaction required beyond low-privilege authentication. No public exploit code has been identified at time of analysis, EPSS sits at 0.34% (27th percentile), and SSVC designates exploitation as 'none' currently - though the SSVC technical impact is rated 'total', confirming the severity of successful exploitation.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by remote attackers holding low-privilege credentials via server-side code injection (CWE-94). The CVSS score of 8.8 reflects full confidentiality, integrity, and availability impact with a low-complexity network attack path requiring only valid user authentication. No public exploitation has been confirmed - EPSS places the exploitation probability at 0.36% (29th percentile) and SSVC rates exploitation status as none and the attack as non-automatable, though SSVC's technical impact rating is total, consistent with arbitrary code execution.
Remote code execution in IBM Langflow OSS 1.0.0-1.10.3 allows authenticated remote attackers to inject and execute arbitrary Python code by crafting payloads that evade the platform's AST-based security scanning mechanism. The flaw (CWE-94, Code Injection) is particularly insidious because the defensive AST validation layer gives a false sense of protection while silently passing malicious constructs to the Python runtime. No public exploit or CISA KEV listing exists at time of analysis, but the low-complexity, fully network-accessible attack path with complete confidentiality, integrity, and availability impact warrants urgent patching - especially for any internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0-1.10.3 allows authenticated low-privilege users to trigger arbitrary Python execution on the backend server by submitting crafted Agentic Assistant workflows containing malicious LLM-generated components that are evaluated server-side during validation before user approval is granted. The flaw (CWE-94, Code Injection) arises because the validation pipeline eagerly executes model-generated Python without sandboxing or deferral, giving attackers backend process-level privileges to exfiltrate data, interact with the file system, or initiate outbound network connections. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS places exploitation probability at 0.22% (13th percentile), but SSVC rates technical impact as total, making this a high-priority patch target for multi-user or internet-exposed deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 allows any internet-reachable attacker to execute arbitrary server-side code using only two HTTP requests. The vulnerability is rooted in CWE-94 (Code Injection), enabling full server compromise with no user interaction. A vendor patch is available via IBM advisory, and no public exploit has been identified at time of analysis - however the trivially low attack complexity makes any internet-exposed instance an immediate remediation priority.
Remote code execution in IBM Langflow OSS (versions 1.0.0 through 1.10.3) allows authenticated attackers to execute arbitrary Python code by exploiting a cryptographic weakness (CWE-326) in the custom component validation mechanism. When the optional hardening mode is enabled - the feature intended to restrict execution to trusted component templates - the application validates submitted component code against a truncated SHA-256 digest, making it computationally feasible for an attacker to craft a malicious Python file that collides with a trusted template's hash and bypasses the validation gate entirely. No public exploit code has been identified at time of analysis; a vendor patch is available per IBM advisory, though the exact fixed version is not stated in available data.
Remote code injection in IBM Langflow OSS 1.0.0 through 1.10.3 allows an authenticated remote attacker to execute arbitrary code on the underlying server by supplying malicious input through user-controlled code fields within the platform. The CVSS vector (AV:N/AC:L/PR:L) confirms the attack is network-reachable at low complexity, requiring only low-privilege credentials, with full confidentiality, integrity, and availability impact on the host. A vendor patch is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Path traversal in IBM Langflow OSS versions 1.0.0 through 1.10.3 enables authenticated remote attackers to read arbitrary files on the underlying system by submitting URLs containing dot-dot sequences (/../). The CVSS scope change metric (S:C) confirms that exploitation reaches beyond the application's own directory boundary, exposing system-level files such as credentials, configuration, or private keys to any low-privileged account holder. No public exploit code has been identified at time of analysis, though IBM has released a patch via advisory node/7282647.
Cross-user chat history disclosure in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to read other users' conversation history by exploiting session_id collision in the MemoryComponent. The MemoryComponent.retrieve_messages and store_message methods validate only session_id when filtering records, omitting flow_id and user_id ownership checks, which exposes multiple REST API endpoints to unauthorized cross-user data access. No public exploit has been identified at time of analysis, but the straightforward exploitation path and High confidentiality impact make this a genuine remediation priority for any multi-user Langflow deployment.
Broken access control in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to inject arbitrary graph data into the shared execution cache for flows they do not own, via the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. The endpoint performs no ownership validation, enabling cross-user cache pollution that can corrupt other users' workflow state, trigger unauthorized execution of foreign flows, or produce denial of service across a shared platform instance. No public exploit code exists and CISA KEV does not list this vulnerability; EPSS (0.20%, 10th percentile) and SSVC (exploitation: none, automatable: no) collectively indicate low immediate exploitation risk despite the high CVSS score.
Predictable Fernet encryption keys in IBM Langflow OSS 1.0.0 through 1.10.3 allow attackers to decrypt stored API keys and authentication tokens, because when a user secret is shorter than 32 characters the platform derives keys with Python's non-cryptographic `random` (Mersenne Twister) module. Because the Mersenne Twister PRNG is deterministic, identical seeds reproduce identical keys, so an adversary who can reconstruct the seeding conditions can regenerate the key and read every secret Langflow encrypted with it. No public exploit identified at time of analysis; EPSS is low (0.11%) and CISA SSVC records no known exploitation.
Predictable Fernet encryption key generation in IBM Langflow OSS (versions 1.0.0 through 1.10.3) stems from the ensure_fernet_key() function deriving keys from a cryptographically weak source (CWE-338), letting an attacker reconstruct the symmetric key that protects stored secrets such as API keys, credentials, and connection variables. Because the key is guessable rather than random, an actor who can read Langflow's encrypted data store can decrypt it and, depending on how the key is reused, potentially forge or tamper with protected values. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), but IBM rates the flaw CVSS 9.8 and a vendor patch is available.
Server-Side Request Forgery in IBM Langflow OSS 1.0.0 through 1.10.3 enables authenticated low-privilege users to coerce the application server into issuing arbitrary outbound HTTP requests against internal infrastructure. The root cause is unsanitized pass-through of the OLLAMA_BASE_URL parameter directly into requests.get() inside validate_model_provider_key(), with no scheme enforcement, host allowlisting, or private-range (loopback, RFC1918, link-local) filtering. No active exploitation confirmed (not in CISA KEV), but the network-accessible, low-complexity attack path and high confidentiality impact (C:H) make this a meaningful internal-network pivot risk for organizations running Langflow with AI provider integration enabled.
OS command injection in IBM Langflow OSS 1.0.0 through 1.10.3 enables remote authenticated attackers to execute arbitrary system commands on the underlying server. The flaw stems from insufficient sanitization of user-supplied input passed to OS-level command execution routines (CWE-78), granting full system-level access with a single authenticated request. No public exploit code has been identified at time of analysis, and CISA does not list this in KEV, though CVSS-assessed technical impact is total across confidentiality, integrity, and availability.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.10.3 is reachable by any authenticated low-privileged user who can modify MCP server configurations. Improper validation of the command field in those configurations allows injected shell commands to be executed with the application's process privileges, yielding full confidentiality, integrity, and availability impact. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, network-accessible attack path against a growing AI-tooling platform warrants prompt patching.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.3 allows authenticated remote attackers to run arbitrary commands by supplying crafted configuration parameters that bypass the application's incomplete input denylist (CWE-184). The flaw carries a CVSS 8.8 score with full confidentiality, integrity, and availability impact, and SSVC rates the technical impact as total. No active exploitation is confirmed - EPSS sits at 0.42% (35th percentile) and the vulnerability is absent from CISA KEV - though the low attack complexity makes it a genuine priority for any internet-exposed Langflow deployment with untrusted authenticated users.
Host filesystem read and write access in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by any authenticated low-privilege user via insufficient filtering of Docker volume-mount and device-mapping arguments passed to Docker-based MCP servers. By injecting unsanitized flags such as --volume into MCP server configuration, an attacker can bind-mount arbitrary host directories into a spawned container, exposing or tampering with sensitive files outside the intended Docker isolation boundary. No public exploit code has been identified at time of analysis and no CISA KEV listing exists, but the network-exploitable, low-complexity attack path and full CIA impact score (CVSS 8.8) make this a high-priority patch target for any organization running Langflow in Docker environments with externally accessible or multi-tenant access.
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.3 exposes the Model Context Protocol (MCP) composer endpoint to unauthenticated remote access when projects are configured with auth_type=oauth and MCP composer is enabled - which is the default deployment state. An unauthenticated network attacker can reach the MCP composer endpoint and read confidential project data (C:H) without supplying valid credentials, entirely bypassing the OAuth authentication gate. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vendor (IBM) has confirmed the issue and released a patch.
Remote authenticated attackers can bypass localhost-only access restrictions in IBM Langflow OSS 1.0.0 through 1.10.3 to write arbitrary MCP (Model Context Protocol) server configurations to IDE configuration files on the underlying host system. The CVSS scope change (S:C) confirms this escapes the Langflow application boundary, enabling persistent manipulation of developer IDE environments on the host. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is available.
Remote code injection in IBM Langflow OSS versions 1.0.0 through 1.10.0 allows an authenticated remote attacker to execute arbitrary code on the underlying host by supplying malicious user-controlled code that is improperly validated (CWE-94). Because Langflow evaluates user-supplied code as part of its low-code AI/agent flow-building functionality, exploitation grants full compromise of the server hosting the application. There is no public exploit identified at time of analysis, but the CVSS 3.1 base score of 9.9 with a scope change reflects that a successful attack can break out of the application context to affect other system components.
Cross-tenant vector document disclosure in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privilege user read another user's private Chroma-backed documents by building a flow that reuses the victim's persist_directory and collection_name, returning exact victim content in the attacker's workflow output. The same shared-namespace flaw also lets the attacker write their own documents into the victim's collection, corrupting its integrity. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as none, but the CVSS 8.1 rating reflects the combined high confidentiality and integrity impact.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.1 stems from improper input validation in the PythonREPL sandbox, allowing a low-privileged authenticated user to escape the sandbox and run arbitrary Python. Because the flaw carries a scope-changing CVSS 3.1 score of 9.9 (S:C, C/I/A all High), a successful exploit can compromise the underlying host beyond the intended sandbox boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Arbitrary file read in IBM Langflow OSS versions 1.0.0 through 1.10.1 allows remote unauthenticated attackers to retrieve files outside the intended web root by submitting URLs containing directory-traversal ("../") sequences. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, exploitation needs no authentication or user interaction and can expose sensitive files such as configuration, secrets, or source code. No public exploit identified at time of analysis, and there is no indication of active exploitation.
Broken object-level authorization in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privileged user read and tamper with build jobs belonging to other users by abusing improper access control on log-retrieval and unauthenticated build endpoints. Because Langflow orchestrates LLM/agent workflow builds, a cross-tenant attacker can view sensitive build logs (high confidentiality impact) and interfere with others' jobs (limited availability impact). A vendor patch is available; there is no public exploit identified at time of analysis and the flaw is not on CISA KEV.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.1 allows remote attackers to run arbitrary OS commands by injecting shell-control environment variables into the MCP (Model Context Protocol) stdio launcher. The DANGEROUS_ENV_VARS blocklist in src/lfx/src/lfx/base/mcp/util.py omits SHELLOPTS, BASHOPTS, and PS4, letting an attacker abuse Bash's xtrace behavior to execute commands when a stdio-based MCP server subprocess is spawned. Rated CVSS 9.8 with a network, no-privilege, no-interaction vector; a vendor patch is available, but no public exploit code or CISA KEV listing has been identified at the time of analysis.
Cross-user information disclosure in IBM Langflow OSS 1.0.0-1.10.1 allows authenticated attackers to access private vector content and poison query results by reusing another user's FAISS namespace. This leads to high confidentiality impact and low integrity impact; the vulnerability has a CVSS 3.1 score of 7.1, and a vendor patch is available.
Cross-user file access in IBM Langflow OSS (1.0.0 through 1.10.1) lets an authenticated user abuse the SaveToFile component to read and modify files uploaded by other users by supplying absolute paths that point into victim storage locations. Append mode enables exfiltration of victim data into the attacker's namespace (confidentiality), while overwrite mode allows replacing victim content with arbitrary data (integrity), collapsing the per-user storage ownership boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available.
Authentication bypass and full data compromise affects IBM Langflow OSS 1.0.0 through 1.10.1, which ships hard-coded credentials (a static password or cryptographic key) embedded in the application. Because the same secret is present in every deployment, remote attackers who read it from the public source or a binary can authenticate to inbound interfaces, impersonate the app to external components, or decrypt internal data on any affected instance. No public exploit identified at time of analysis, but the shared-secret nature makes exploitation trivial once the value is known.
Arbitrary file write in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated user create a malicious flow that points to an attacker-controlled URL returning a crafted Content-Disposition header, causing the Langflow process to write attacker-supplied content to any filesystem path it can access. Because writes can land on startup scripts, keys, or configuration files, this path-traversal (CWE-22) flaw is a realistic route to full server compromise. IBM has released a fix; no public exploit identified at time of analysis and the CVE is not in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows an authenticated remote attacker to run arbitrary code because validation is not fully enforced on Model Context Protocol (MCP) server configuration files, permitting injection of attacker-controlled commands or server definitions. IBM has published a fix advisory (node/7278932). With CVSS 8.8 (PR:L), a low-privileged user of the Langflow instance can escalate to full code execution on the host; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Arbitrary file read in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated attacker traverse the filesystem to exfiltrate sensitive files - most critically the JWT signing key - and then forge valid authentication tokens to impersonate any user, including administrators. The path-traversal-to-account-takeover chain turns a low-privilege foothold into full application compromise. No public exploit identified at time of analysis, and the EPSS score is low (0.38%, 31st percentile), but a vendor patch is available and the impact is severe.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows authenticated users to override arbitrary component parameters at runtime through the API, bypassing the parameter filtering logic in the apply_tweaks() function (CWE-94 code injection). Because a low-privileged authenticated account is sufficient and the impact is full compromise of confidentiality, integrity, and availability (CVSS 8.8), this maps to server-side code execution on the Langflow host. There is no public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows attackers to run arbitrary code by planting a malicious pickle payload that the AsyncDiskCache deserializes with unauthenticated pickle.loads(). Any actor able to influence cached data - via file system access, crafted workflow inputs, custom components, or API manipulation - gains full compromise at the privilege of the Langflow server process. Rated CVSS 9.9 and reported by IBM with a vendor patch available; no public exploit identified at time of analysis.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 lets any logged-in user run arbitrary Python — and therefore arbitrary OS commands — with the privileges of the Langflow server process. The flaw is a design failure in the POST /api/v1/validate/code endpoint, which passes user-supplied code straight into Python's exec() with no sandbox, validation, or privilege drop. Rated CVSS 9.9 by IBM; no public exploit identified at time of analysis, though the trivial exec()-based trigger makes exploitation straightforward once authenticated.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 stems from broken webhook authentication that skips API key validation whenever WEBHOOK_AUTH_ENABLE is False - which is the shipped default. Any remote attacker who learns a flow's UUID can invoke that flow's webhook endpoint as though they were its owner, running arbitrary flow logic and reaching RCE. No public exploit identified at time of analysis, but the CVSS 9.8 rating and default-vulnerable configuration make this a high-priority patch.
Privilege escalation to remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 allows an authenticated user to elevate their account to superuser by directly manipulating the underlying database, then execute arbitrary system commands and achieve full compromise of the host running the Langflow service. The flaw (CWE-94, code injection) carries a critical CVSS 9.9 with a scope change, meaning code runs with the Langflow service account's permissions beyond the vulnerable component. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but a vendor patch is available.
Arbitrary file write in IBM Langflow OSS 1.0.0 through 1.10.0 lets an attacker who controls an external HTTP server plant files at attacker-chosen paths on the Langflow host. The flaw lives in the APIRequest component's 'Save to File' feature, which trusts filenames from a response Content-Disposition header without sanitizing path traversal sequences, so a malicious server response can escape the temporary directory and write to any location the Langflow process can reach. No public exploit identified at time of analysis, and it is not in CISA KEV; a patch is available per IBM's advisory.
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.0 lets an unauthenticated remote attacker retrieve a long-lived superuser bearer token from the /api/v1/login/auto_login endpoint whenever the AUTO_LOGIN setting is on - which is the default. Because the endpoint mints full-admin tokens with no credentials, any network-reachable attacker gains complete administrative control, and overly permissive CORS can leak those tokens to unintended origins. A vendor patch is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0 through 1.10.0 (Langflow versions up to 1.9.2) allows authenticated users with flow-creation privileges to bypass the allow_custom_components=false control via the Policies component's ToolGuard integration. Because validation only inspects the main component code and ignores dynamic CodeInput fields, attackers persist malicious Python in a flow that runs server-side when a guarded tool executes. No public exploit has been identified at time of analysis, but the flaw is IBM-confirmed with a vendor patch and carries a critical 9.9 CVSS due to cross-tenant escalation through the agentic MCP update_flow_component_field tool.
Unauthenticated remote code execution in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets any network-reachable attacker achieve full RCE on default deployments by chaining two endpoints: /api/v1/auto_login, which mints SUPERUSER tokens to any caller, and /api/v1/validate/code, which passes user-supplied code to Python's exec(). CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N) and a vendor patch is available; there is no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Missing authentication in IBM Langflow OSS 1.0.0 through 1.10.0 lets unauthenticated remote attackers register unlimited user accounts against any exposed instance. When the documented NEW_USER_IS_ACTIVE=true option is set, those accounts become immediately active and can log in to reach known remote-code-execution endpoints, providing a full authentication foothold without relying on AUTO_LOGIN. No public exploit identified at time of analysis, but the CVSS 9.8 rating and unauthenticated network vector make internet-facing deployments a high priority.
Improper authorization enforcement in IBM Langflow OSS 1.0.0 through 1.9.6 lets unauthenticated remote attackers reach protected MCP (Model Context Protocol) project resources and invoke MCP operations through the Streamable MCP transport endpoint. Because the flaw bypasses authentication entirely on a network-facing endpoint and is rated CVSS 9.8 with full confidentiality, integrity, and availability impact, any exposed Langflow instance is at risk. There is no public exploit identified at time of analysis, and the EPSS probability is low (0.24%, 15th percentile), indicating exploitation has not yet become widespread.
Arbitrary code execution in IBM Langflow OSS versions 1.0.0 through 1.10.0 allows remote attackers to run code on the host by submitting flow definitions containing nodes with missing or empty component type fields. The improper input validation (CWE-20) lets malformed node specifications bypass type checks and reach unsafe execution paths in the low-code AI workflow engine. The CVSS vector (AV:N/PR:N) indicates network-reachable, pre-authentication exploitation; no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Insecure deserialization (CWE-502) in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets any party with access to the backing Redis store inject a malicious serialized object that Langflow deserializes, yielding arbitrary code execution with full application privileges. Successful exploitation exposes all stored secrets, flow data, and the underlying host, effectively a complete compromise of the Langflow instance. No public exploit has been identified at time of analysis, and the issue is not listed in CISA KEV; a vendor patch is available per IBM advisory node 7278443.
Code injection in IBM Langflow OSS versions 1.0.0 through 1.10.0 lets an authenticated user execute arbitrary operating-system commands and read sensitive files such as stored credentials, escalating from low-privileged application access to full host compromise. Rated CVSS 9.9 with a scope-changing vector, the flaw enables lateral movement once an attacker holds any valid Langflow account. No public exploit identified at time of analysis, but a vendor patch is available.
Credential disclosure in IBM Langflow OSS versions 1.0.0 through 1.10.0 stems from a weak, reversible key-derivation mechanism used to protect secrets encrypted at rest, allowing an attacker who can reach the stored credential data to recover the encryption key and decrypt every stored credential. Because Langflow stores API keys, database connection strings, and third-party service tokens used by AI workflow components, recovery of these secrets gives an attacker the keys to all integrated systems. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score supplied, so the threat is currently theoretical but high-impact, and IBM (the reporter) has released a fix.
Authorization bypass in IBM Langflow OSS 1.0.0 through 1.8.4 allows unauthenticated remote attackers to access protected Model Context Protocol (MCP) project resources and invoke MCP operations through the Streamable MCP transport endpoint. The CVSS 9.8 rating reflects unauthenticated network exploitation with full confidentiality, integrity, and availability impact, though no public exploit identified at time of analysis and the flaw is not currently listed in CISA KEV.