What is CVE-2026-9198?

CVE-2026-9198 is Unauthenticated Remote Code Execution via Auto-Login Bypass and Code Validation. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-94 Code Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

22 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-9198 using CVSS 9.8, EPSS 35%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalRemote Code Execpublic exploit

CVE-2026-9198

CVE-2026-9198 — Unauthenticated Remote Code Execution via Auto-Login Bypass and Code Validation

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-9198 in CISA KEV with required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Jul 17, 2026Updated Aug 17, 2026Sources: NVD, IBM (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 4, 2026

EPSS

35%

ahead of 98% of scored CVEs

Affects

IBM

Langflow OSS

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

IBM strongly recommends addressing the vulnerability now by upgrading Langflow OSS to version 1.10.1 https://pypi.org/project/langflow/

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Federal deadline Aug 7, 2026 — passed 40 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
IBM	Langflow OSS	1.0.0 to <= 1.10.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	IBM (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-94 · Improper Control of Generation of Code ('Code Injection')

Bypass Protection Mechanism
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands
Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

Weakness & attack patterns

CWE-94Code Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-77 · Manipulating User-Controlled VariablesCAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1027.006Obfuscated Files or Information: HTML Smuggling
T1027.009Obfuscated Files or Information: Embedded Payloads
T1564.009Hide Artifacts: Resource Forking

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 4, 2026

Federal deadline

Aug 7, 2026

passed 40 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

20 more posts on this CVEShowing 5 of 25 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /api/v1/auto_login, /api/v1/validate/code.
Prioritize edge telemetry for network-reachable Langflow OSS.
Monitor for scanner or exploit-pattern traffic after 22 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited chessalekin/cve-2026-9198_exploit
Aug 24, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.8 (AV:N)
Aug 17, 2026 · NVD
Cve is exploited rmhowe425/PoC-CVE-2026-9198
Aug 6, 2026 · SOCRadar CTI
Added to CISA KEV catalog
Aug 4, 2026 · CISA
Initial · CVE published
Jul 17, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

15×SVRS was changedAug 1, 2026 – Aug 29, 2026 · SOCRadar CTI
9×TweetsJul 31, 2026 – Aug 19, 2026 · SOCRadar CTI
5×Github ReposAug 5, 2026 – Aug 23, 2026 · SOCRadar CTI
3×TelegramAug 1, 2026 – Aug 29, 2026 · SOCRadar CTI
3×ModifiedAug 4, 2026 – Aug 5, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Aug 5, 2026 · SOCRadar CTI

References

5 on the record

www.ibm.com/support/pages/node/7278927
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-9198
US Government Resource, NIST
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2026-9198
Vendor Advisory

Coverage

9 stories from the feeds we poll

4 more reports on this CVEShowing 5 of 9 · Vendor research and security press coverageUnlock free

Elsewhere on this site

IBMevery CVE for this vendor
August 2026what else CISA listed
Remote Code Execsame class
CWE-94other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-9198 is Unauthenticated Remote Code Execution via Auto-Login Bypass and Code Validation, a critical vulnerability affecting Langflow OSS from IBM. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 22 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 35% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.