cve.bz

CVE-2026-9198 IBM Langflow Code Injection Vulnerability

9.8 criticalKEVExploitEPSS 29%

Critical (9.8) in IBM Langflow. In CISA KEV since 2026-08-04. EPSS 29% estimated probability of exploitation activity in the next 30 days.

On this page
IBM Langflow OSS 1.0.0 through 1.10.0 allows unauthenticated attackers to chain /api/v1/auto_login (mints SUPERUSER tokens to any network caller) with /api/v1/validate/code (executes user code via exec()) to achieve full RCE on default Langflow deployments

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
29% (unchanged from 29% a week ago; 29% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-08-04, due 2026-08-07
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-9198 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9198?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9198?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9198 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
IBM Langflow OSSfrom 1.0.0 through 1.10.0

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • 0xgh057r3c0n/CVE-2026-9198 Harbor Check: matches CVE 3 stars, Python, created
    IBM Langflow Unauthenticated RCE via Auto-Login Bypass
  • 0xdak/CVE-2026-9198_exploit Harbor Check: matches CVE 2 stars, Python, created
  • rmhowe425/PoC-CVE-2026-9198 Harbor Check: matches CVE 1 star, Python, created
    Proof of concept exploit code for CVE-2026-9198
  • Edward-w-Jack/CVE-2026-9198 Harbor Check: matches CVE 0 stars, Python, created
    PoC for CVE-2026-9198
  • Riftweld/langflow-cve-2026-9198 Harbor Check: matches CVE 0 stars, Python, created
    Independent reconstruction, lab validation, and PoC for CVE-2026-9198, the Langflow unauthenticated RCE (fixed in 1.10.1)
4 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Nuclei template IBM Langflow - Remote Code Execution
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Langflow auto-login Token Minting (CVE-2026-9198) sid 2072661
  • Emerging Threats Open ET WEB_SPECIFIC_APPS IBM Langflow Auto-Login Bypass (CVE-2026-9198) sid 2071355

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON