CVE-2026-7700 — The Function Eval Of The File Src/Lfx/Src/Lfx/Components/Llm Vulnerability
CVE-2026-7700 — A weakness has been identified in langflow-ai langflow up to 1.8.4. This affects the function eval of the file src/lfx/src/lfx/components/llm_operations/lambda_filter.p of the component LambdaFilterComponent. Executing a manipulation can lead to code injection. The attack may be perf
What This Means For You
- If your environment is affected by CWE-74, CWE-94, review your exposure and prioritize patching based on your environment. Monitor vendor advisories for CVE-2026-7700 updates and patches.
Related ATT&CK Techniques
🛡️ Detection Rules
3 rules · 6 SIEM formats3 detection rules auto-generated for this incident, mapped to MITRE ATT&CK. Sigma YAML is free — export to any SIEM format via the Intel Bot.
CVE-2026-7700 - Langflow LambdaFilterComponent Code Injection
title: CVE-2026-7700 - Langflow LambdaFilterComponent Code Injection
id: scw-2026-05-03-ai-1
status: experimental
level: critical
description: |
Detects potential exploitation attempts against CVE-2026-7700 in Langflow. This rule specifically targets requests to the '/api/v1/process' endpoint with 'lambda_filter.p' in the query, looking for indicators of code injection within the URI query parameters. This is the primary detection for initial exploitation via the vulnerable LambdaFilterComponent.
author: SCW Feed Engine (AI-generated)
date: 2026-05-03
references:
- https://shimiscyberworld.com/posts/nvd-CVE-2026-7700/
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection:
cs-uri|contains:
- '/api/v1/process'
cs-method|exact:
- 'POST'
cs-uri-query|contains:
- 'lambda_filter.p'
# The actual payload will vary, but look for common code injection patterns within the request body or query parameters
# This is a placeholder for a more specific payload detection if available.
# Example: A generic indicator of code execution within a query parameter related to lambda_filter.p
# For a real-world scenario, you would analyze actual exploit payloads.
# Example: If the payload is passed in a JSON body, a webserver log might not capture it directly.
# This rule assumes some part of the exploit is visible in URI or query for webserver logs.
selection_indicators:
# This is a highly simplified example. Real-world detection would require analyzing the specific exploit payload.
# For instance, if the exploit uses Python's eval with untrusted input, look for suspicious function calls.
# This example looks for a common pattern that might appear in a query string if the exploit is poorly constructed.
cs-uri-query|contains:
- 'eval('
- 'exec('
- 'import os'
- 'import subprocess'
condition: selection AND selection_indicators
falsepositives:
- Legitimate administrative activity
Source: Shimi's Cyber World · License & reuse
Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| CVE-2026-7700 | vulnerability | CVE-2026-7700 |
| CWE-74 | weakness | CWE-74 |
| CWE-94 | weakness | CWE-94 |
Source & Attribution
| Source Platform | NVD |
| Channel | National Vulnerability Database |
| Published | May 03, 2026 at 18:15 UTC |
This content was curated and summarized by Shimi's Cyber World for informational purposes. It is not copied or republished in full. All intellectual property rights remain with the original author and source.
Believe this infringes your rights? Submit a takedown request.