langflow-ai · Langflow · published 2026-03-20

CVE-2026-33053Langflow has Missing Ownership Verification in API Key Deletion (IDOR)

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-33053 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 39% of all CVEs. This Langflow vulnerability: CVSS 6.1 (v4.0). Fixed upstream in Langflow 1.9.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Langflow 1.9.0.

Patch events

  1. Patch todaySecurity release

    AI toolingLangflow

    Langflow security release: 1.9.0

    Upgrade to 1.9.0

    Why: CVE-2026-33017: Known exploited server software, exploitation is automatable, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (39th pct)FIRST EPSS v2026.06.15
CVSS base score6.1 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:L
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the delete_api_key_route() endpoint accepts an api_key_id path parameter and deletes it with only a generic authentication check (get_current_active_user dependency). However, the delete_api_key() CRUD function does NOT verify that the API key belongs to the current user before deletion.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →