3-minute product tour Urgent incident email
Urgent security advisory

Mitigation guidance for the Langflow remote code execution vulnerability (CVE-2026-33017)

See which Langflow versions are affected, how to update them, and how to investigate signs of compromise.
The advisory also covers follow-up actions such as rotating secrets used on the affected server.

Mitigation guidance for the Langflow remote code execution vulnerability (CVE-2026-33017)

Summary

CVECVE-2026-33017 (GHSA-vwmf-pq79-vjvx)
ProductLangflow (PyPI package langflow)
TypeMissing authentication (CWE-306) and code injection (CWE-94)
SeverityCVSS 4.0 score of 9.3 (Critical), according to the GitHub Security Advisory
Affected Versions1.8.2 and earlier (GitHub Security Advisory)
Minimum patched version1.9.0
Known ExploitationCISA KEV listing, March 25, 2026. Remediation deadline for U.S. federal agencies, April 8, 2026.

What went wrong

Affected versions inadequately validated untrusted input for some unauthenticated public flow requests. This could allow remote code execution with the Langflow process’s privileges. The impact depends on what files, environment variables, and other systems the service account can access.

CVE-2025-3248 is a separate Langflow vulnerability. Confirm that your deployed version includes the CVE-2026-33017 fix even if you addressed the earlier issue.

Observed exploitation

CISA added this vulnerability to its Known Exploited Vulnerabilities (KEV) Catalog. Sysdig reported observing exploitation activity against publicly exposed Langflow deployments shortly after disclosure. If your deployment was internet-facing, investigate for compromise as well as updating it.

Correlate unusual public flow requests with unexpected child processes from Langflow, new outbound connections, and unexpected file changes during the same period.

Mitigation

  1. Update to 1.9.0 or later. For production, use a security release the vendor currently supports and verify the version of the running package or container image.
  2. Restrict direct internet access to Langflow until the update is complete. If you require public flows, review the network and proxy policies to limit access to approved users.
  3. If a vulnerable version was exposed externally, investigate for compromise. Revoke or rotate accessible API keys, database passwords, and cloud credentials as needed.
  4. Production deployments LANGFLOW_AUTO_LOGINto false and require account authentication.

Indicators to Review

  • Review the reverse proxy and application logs for the timestamps, sources, and outcomes of public flow requests.
  • Correlate processes started during the same period with outbound connections, file changes, and access to secrets.
  • Legitimate public flows may use the same path. Consider the request path alongside other evidence when assessing compromise, and preserve relevant records for follow-up analysis.

References

Talk to Genox
about scope and timing.

Talk to us