NewIntroducing ISO360 — our all-in-one ISO compliance platform
R4IM — Room for Improvement
All advisories
CVE-2026-9198CRITICAL · CVSS 9.8 Actively Exploited

CVE-2026-9198

langflow · langflow

What's the vulnerability?

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

R4IM analyst take

Business impact & how R4IM helps

This advisory is on our active-exploitation watchlist. Attackers are using it for initial access, privilege escalation or lateral movement in real-world intrusions. R4IM's offensive security and SOC teams already have detections, exploit replicas and remediation playbooks for this issue.

Validate your exposure

Targeted vulnerability assessment to confirm which of your assets are actually exploitable — not just theoretically affected.

Prove it with a pentest

Our pentesters chain this CVE into realistic attack paths so you see business impact, not just a scan finding.

Web app security testing

If the affected product is internet-facing, our AppSec team will harden it against this and related OWASP-class issues.

24/7 SOC & detection

Continuous monitoring with custom detections for this CVE deployed across your endpoints, identity and cloud.

Talk to a security engineer →

Recommended remediation

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.
  1. Inventory all assets running the affected vendor and product, including shadow IT and third-party hosted instances.
  2. Apply the vendor patch or mitigation referenced in the advisories below. Where no patch exists, isolate the asset or restrict network exposure.
  3. Hunt for indicators of prior compromise — exploitation of this class of bug often predates public disclosure.
  4. Deploy detections for the exploit primitives (network signature, EDR rule, WAF rule) and re-test after remediation.

Need help executing these steps? Our team typically completes validation and remediation within a single patch cycle. Request remediation support →

Vendor & research references