CVE-2026-33475
Unauthenticated shell injection in Langflow GitHub Actions leads to RCE and secret exfiltration.
Is CVE-2026-33475 being exploited?
Not confirmed. CVE-2026-33475 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 3.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-33475?
CVE-2026-33475 is rated Critical with a CVSS score of 9.1. 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-33475?
Yes. A fix has been recorded for CVE-2026-33475. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33475 affect?
CVE-2026-33475 affects Langflow, GitHub Actions, CI/CD runners, Workflow files (.github). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33475?
Upgrade to Langflow 1.9.0+; sanitize inputs; rotate secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CI shell injection enables remote code execution and exfiltration of secrets (GITHUB_TOKEN) via untrusted inputs.
Immediate action required
- affected< 1.9.0
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.