Skip to content
AI/ML

CVE-2026-17632

8.8
High
EPSS 0.45%Patch availableAug 6, 2026

Authenticated RCE in IBM Langflow OSS via unsafe AST Python validation.

common questions

Is CVE-2026-17632 being exploited?

Not confirmed. CVE-2026-17632 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-17632?

CVE-2026-17632 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-17632?

Yes. A fix has been recorded for CVE-2026-17632. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-17632 affect?

CVE-2026-17632 affects IBM Langflow OSS 1.0.0 - 1.10.3, Langflow Python-based deployments, Servers running AST-based security scanning. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17632?

Restrict access, revoke suspicious creds, monitor logs; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Langflow OSS 1.0.0 - 1.10.3Langflow Python-based deploymentsServers running AST-based security scanning
impact

Authenticated remote attacker can execute arbitrary Python code on Langflow servers, enabling full server compromise and data exfiltration.

action required

Immediate action required

affected versions
IBM Langflow OSS
  • affected>= 1.0.0 and <= 1.10.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free