Critical IBM Langflow Flaw CVE-2026-9198 (CVSS 9.8) Added to CISA KEV (August 2026)

Our automated tracking framework flagged that CISA added CVE-2026-9198 (IBM Langflow) to the Known Exploited Vulnerabilities (KEV) catalog on August 5, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild — U.S. federal agencies must patch it by a fixed deadline. Here is what our data shows.

What CISA Reported

CISA describes the flaw as follows: “Langflow contains a code injection vulnerability that allows unauthenticated attackers to achieve full remote code execution on default Langflow deployments.”

Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-9198 by August 7, 2026 — a 3-day window. Private organizations are not bound by the deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

The Details

How This Compares to IBM’s Track Record

This one was public for just 18 days before CISA confirmed exploitation — faster than IBM’s 545-day median, meaning attackers moved unusually quickly. IBM currently ranks #20 on our KEV Lag leaderboard.

For perspective, the median across all 1660 tracked KEV entries is 272 days — IBM’s exploited vulnerabilities are flagged slower than the catalog average.

Other Recent IBM KEV Additions

The most recent IBM vulnerabilities CISA has confirmed as actively exploited, from our tracker:

What This Means for Defenders

CISA has added CVE-2026-9198, an IBM Langflow Code Injection Vulnerability with a critical CVSS base score of 9.8, to its Known Exploited Vulnerabilities (KEV) catalog. This necessitates immediate attention from all organizations, particularly federal agencies facing an August 7, 2026 patch deadline. Given the code injection nature, successful exploitation allows attackers to execute arbitrary code, potentially leading to full system compromise, data exfiltration, or further network penetration. Any organization using IBM Langflow should prioritize patching this vulnerability without delay.

The vulnerability was public for 18 days before its inclusion in the KEV catalog, indicating that active exploitation was detected relatively quickly after disclosure. While ransomware use has not been confirmed for this specific CVE, the speed of KEV listing points to a high probability of widespread and opportunistic exploitation by various threat actors. The critical severity demands that security teams treat this as an urgent matter, regardless of their specific threat profile.

For systems where immediate patching before the August 7 deadline is not feasible, implementing robust compensating controls is crucial. This includes isolating affected IBM Langflow instances, applying strict network segmentation, monitoring for unusual activity originating from or targeting these systems, and ensuring comprehensive logging is enabled. Organizations should also consider web application firewalls (WAFs) and intrusion detection/prevention systems (IDS/IPS) to detect and block exploitation attempts while a permanent patch is being deployed.

Related Coverage

• Cisco’s CVE-2026-20316 Was Exploited in 0 Days — Well Under Its 1245-Day Median (July 2026)
• WordPress’s CVE-2026-63030 Was Exploited in 4 Days — Well Under Its 420-Day Median (July 2026)

How We Track This

This report was generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No dates or figures on this page are estimated or taken from third-party sources — they come directly from CISA and NVD records.