CVE-2026-33017 Google Chronicle · YARA-L

Detect CVE-2026-33017: Langflow Code Injection Vulnerability in Google Chronicle

Detects exploitation of CVE-2026-33017, a code injection vulnerability in Langflow that allows unauthenticated or low-privileged attackers to execute arbitrary code via the Langflow API. The vulnerability stems from improper input validation (CWE-94/CWE-95) combined with missing authentication controls (CWE-306), enabling remote code execution against Langflow instances. This CVE is on the CISA KEV list, indicating active exploitation in the wild.

MITRE ATT&CK

Tactic
Initial Access Execution Privilege Escalation

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_33017_langflow_code_injection {
  meta:
    author = "df00tech Detection Engineering"
    description = "Detects CVE-2026-33017 Langflow code injection exploitation attempts"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx"
    
  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.network.application_protocol = "HTTP"
    (
      $http.target.port = 7860 or
      $http.target.port = 7861 or
      $http.target.port = 3000
    )
    (
      $http.network.http.request_url = /\/api\/v1\/(run|process|predict|build)/
    )
    (
      $http.network.http.request_body = /__import__|exec\(|eval\(|os\.system|subprocess|__builtins__|socket\./
    )
    
  condition:
    $http
}
critical severity high confidence

Chronicle YARA-L rule detecting HTTP requests to Langflow API endpoints containing Python code injection patterns associated with CVE-2026-33017 exploitation.

Data Sources

Chronicle network telemetryHTTP proxy logs ingested to Chronicle

Required Tables

network_http

False Positives & Tuning

  • Legitimate Langflow API usage where custom Python components are submitted programmatically
  • Development or staging environments where code injection strings appear in test payloads
  • Authorized red team or bug bounty activities targeting Langflow

Other platforms for CVE-2026-33017


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Langflow API Code Injection via /api/v1/run - OS Command Execution

    Expected signal: Web server access log entry showing POST to /api/v1/run with a request body containing 'subprocess' and 'shell=True'. EDR should capture a child process (sh or bash) spawned by the Langflow Python/uvicorn process.

  2. Test 2Langflow Unauthenticated API Access Check - Missing Auth Bypass (CWE-306)

    Expected signal: Web server access log showing a GET request to /api/v1/flows from an external IP with a 200 OK response and no Authorization header present.

  3. Test 3Langflow Code Injection via eval() - Python Builtin Abuse

    Expected signal: HTTP POST request to /api/v1/process containing '__import__' and 'os.system' in the request body. File creation event for /tmp/pwned_cve_2026_33017.txt on the Langflow host. EDR should capture os.system call from the Python process.

  4. Test 4Langflow Reverse Shell Payload Simulation

    Expected signal: Outbound TCP connection from the Langflow host to the attacker IP on port 4444. EDR process event showing /bin/sh spawned by uvicorn/gunicorn with stdin/stdout redirected to a socket. Network flow record of the connection in firewall or NDR logs.

Unlock Pro Content

Get the full detection package for CVE-2026-33017 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections