How many CVEs have patched delete_flow?

1 published CVEs changed delete_flow in langflow-ai/langflow, in 1 distinct patches totalling 1 changed lines, between 2026 and 2026.

What is the latest CVE that changed delete_flow?

CVE-2026-34046 (Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check), published 2026-03-27, changed lines 387 of src/backend/base/langflow/api/v1/flows.py.

How does delete_flow compare to the rest of langflow-ai/langflow?

langflow-ai/langflow has 23 CVEs with a located fix in total; 1 of them changed delete_flow.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

langflow-ai/langflow

Function

delete_flow

Name: delete_flow in langflow-ai/langflow: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/backend/base/langflow/api/v1/flows.py

Last patched March 27, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

1

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

delete_flow in langflow-ai/langflow was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 1 lines in total.

langflow-ai/langflow has 23 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed delete_flow, newest first, with the lines each fix touched.

Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check
CVE-2026-34046 · line 387 · +0 −1
High · CVSS 8.7
EPSS 0.7%2026-03-27

Get an alert when the next CVE fix lands in langflow-ai/langflow, with the patched functions.

Monitor langflow CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in langflow-ai/langflow changed by the most CVE fixes.

download_image3 CVEs · src/backend/base/langflow/api/v1/files.py _resolve_kb_path3 CVEs · src/backend/base/langflow/api/v1/knowledge_bases.py create_knowledge_base3 CVEs · src/backend/base/langflow/api/v1/knowledge_bases.py get_flow_by_id_or_endpoint_name3 CVEs · src/backend/base/langflow/helpers/flow.py get_client_ip2 CVEs · src/backend/base/langflow/api/v1/mcp_projects.py validate_command2 CVEs · src/backend/base/langflow/api/v2/schemas.py

All patched functions in langflow-ai/langflow

Frequently asked questions

Common questions about CVE fixes to delete_flow.

How many CVEs have patched delete_flow?: 1 published CVEs changed delete_flow in langflow-ai/langflow, in 1 distinct patches totalling 1 changed lines, between 2026 and 2026.
What is the latest CVE that changed delete_flow?: CVE-2026-34046 (Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check), published 2026-03-27, changed lines 387 of src/backend/base/langflow/api/v1/flows.py.
How does delete_flow compare to the rest of langflow-ai/langflow?: langflow-ai/langflow has 23 CVEs with a located fix in total; 1 of them changed delete_flow.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track langflow-ai/langflow CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing