Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7700 medium CVSS 6.3

Vulnerability in langflow (CVE-2026-7700)

Summary

Vulnerability in langflow (CVE-2026-7700). Risk of unauthorized operations or information disclosure. Exploitable via LambdaFilterComponent. Mitigation: upgrade to 1.10.3 or later.

Original description

The description as published by the source.

Summary

Langflow versions 1.3.0 through 1.10.2 contain a code-injection vulnerability in the Smart Transform (LambdaFilterComponent) component.

Smart Transform places flow-author instructions and a preview of its input data into a prompt asking an LLM to generate a Python lambda. It then extracts a one-line lambda from the model response, applies only syntactic format checks, evaluates it with Python's full builtins, and invokes the resulting function inside the Langflow process.

A malicious flow author can exploit this directly through the Instructions field. In deployments where an exposed flow passes attacker-controlled content into Smart Transform, an attacker may also exploit it indirectly through prompt injection, subject to the configured model following the injected instruction.

Vulnerability details

Vulnerable Code Location: src/lfx/src/lfx/components/llm_operations/lambda_filter.py (line 242 in v1.10.2)

def _validate_lambda(self, lambda_text: str) -> bool:
    """Validate the provided lambda function text."""
    return lambda_text.strip().startswith("lambda") and ":" in lambda_text

# ...
return eval(lambda_text)  # noqa: S307

For example, an attacker can attempt to make the model return:

lambda x: __import__("os").system("id")

This expression satisfies the vulnerable format checks. eval() creates the lambda with access to Python's default builtins, and the subsequent fn(data) invocation (in _execute_lambda) executes the…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7700 has been found in langflow.
Attackers can target a specific entry point like LambdaFilterComponent over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade langflow to 1.10.3 or later.
If unsure, ask your IT team or search "langflow CVE-2026-7700" on the vendor's site.

CVE-2026-7700 (langflow) — CWE-74 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: LambdaFilterComponent / _execute_lambda
Patched: 1.10.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-74) exists in langflow. Attackers reach the vulnerable code path via LambdaFilterComponent.

📍 Affected scope

Check the vendor advisory for the affected versions of langflow. Attack surface: LambdaFilterComponent / _execute_lambda.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.10.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'langflow' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で langflow を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade langflow to 1.10.3

    ステージング環境で 1.10.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.10.3"}]}]
PyPI langflow
[{"type":"ECOSYSTEM","events":[{"introduced":"1.3.0"},{"fixed":"1.10.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details