Skip to content

SecurityIBM (Langflow)

Fixed

IBM fixes Langflow auto-login RCE chain CVE-2026-9198 in 1.10.1; CISA later lists it as exploited

Langflow OSS at a glance

Langflow OSS 1.0.0 to 1.10.0 handed superuser tokens to any caller via auto_login, which could be chained with the code validation endpoint for unauthenticated RCE. CISA added CVE-2026-9198 to KEV on August 4, 2026.

Langflow OSS: status

FixedCritical
Affected
  • Langflow OSS 1.0.0 through 1.10.0 (CVE-2026-9198)
  • Langflow 1.6.9 and earlier (CVE-2025-34291)
Status as of
Discovered by
Harish Kolla (credited by IBM for CVE-2026-9198)

What changed with Langflow OSS

IBM published a security bulletin on July 2, 2026 for CVE-2026-9198 in Langflow OSS, rated 9.8 (critical). The unauthenticated /api/v1/auto_login endpoint issued superuser bearer tokens to any network caller, and /api/v1/validate/code then executed submitted Python. Chained together, they gave remote code execution on default deployments where auto-login is on and the validation endpoint is reachable.

Versions 1.0.0 through 1.10.0 on Windows, macOS, and Linux are affected. IBM recommends upgrading to Langflow OSS 1.10.1 now and lists no workaround. CISA added the flaw to its Known Exploited Vulnerabilities catalog on August 4, 2026, with a remediation deadline of August 7.

It was Langflow's third KEV listing of 2026. CISA also added CVE-2026-33017 in March and, on May 21, CVE-2025-34291, a flaw in Langflow 1.6.9 and earlier where a permissive CORS setup and a SameSite=None refresh-token cookie let a malicious web page take over a logged-in user's session and reach code execution.

How to fix it: Langflow OSS

  1. 1. Update

    Upgrade Langflow OSS to 1.10.1 or later.

    ibm.com (opens in a new tab)

Advisories

Where to compare Langflow OSS

Independent leaderboards and official resources for comparing this model yourself. Rankings change often; each site shows its own current data.

Why Langflow OSS matters for businesses

Repeated exploitation shows attackers are actively scanning for AI agent builders. If your team runs Langflow for prototypes or client demos, confirm it is on 1.10.1 or later, keep it off the public internet, and treat any instance that was exposed on an older version as possibly compromised, including the API keys stored in its flows.

Sources for this story

  1. Official
  2. CVE-2026-9198 Detail (opens in a new tab)

    NIST National Vulnerability Database · nvd.nist.gov

    Official
  3. CVE-2025-34291 Detail (opens in a new tab)

    NIST National Vulnerability Database · nvd.nist.gov

    Official

Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.

  • #security
  • #cve
  • #langflow
  • #cisa-kev
  • #actively-exploited
  • #agent-builders

Want this working in your business?

We turn new AI capabilities into agents, voice receptionists, and automations you can actually use.