🛡️ CVE-2026-21445 — langflow
Description
Langflow Missing Authentication on Critical API Endpoints
Summary
Multiple critical API endpoints in Langflow are missing authentication controls, allowing any unauthenticated user to access sensitive user conversation data, transaction histories, and perform destructive operations including message deletion. This affects endpoints handling personal data and system operations that should require proper authorization.
Details
The vulnerability exists in three API endpoints within src/backend/base/langflow/api/v1/monitor.py that are missing the required dependencies=[Depends(get_current_active_user)] authentication dependency:
Affected Endpoints:
1. GET /api/v1/monitor/messages (Line 61)
```python
@router.get("/messages") # ❌ Missing authentication
async def get_messages(
session: DbSession,
flow_id: Annotated[UUID | None, Query()] = None,
session_id: Annotated[str | None, Query()] = None,
# ... other parameters
) -> list[MessageResponse]:
```
2. GET /api/v1/monitor/transactions (Line 183)
```python
@router.get("/transactions") # ❌ Missing authentication
async def get_transactions(
flow_id: Annotated[UUID, Query()],
session: DbSession,
params: Annotated[Params | None, Depends(custom_params)],
) -> Page[TransactionTable]:
```
3. DELETE /api/v1/monitor/messages/session/{session_id} (Line 165)
```python
@router.delete("/messages/session/{session_id}", status_code=204) # ❌ Missing authentication
async def delete_messages_session(
session_id: str,
session: DbSession,
):
```
Inconsistency Evidence:
Other endpoints in the same file properly implement authentication:
```python
@router.get("/messages/sessions", dependencies=[Depends(get_current_active_user)]) # ✅ Properly secured
@router.delete("/messages", status_code=204, dependencies=[Depends(get_current_active_user)]) # ✅ Properly secured
```
PoC
Complete reproduction steps to demonstrate the vulnerability:
Prerequisites:
1. Start a Langflow server instance
2. Ensure no authentication headers or API keys are provided
Reproduction Commands:
```bash
# 1. Access all user conversations without authentication
curl http://localhost:7860/api/v1/monitor/messages
# 2. Access transaction history without authentication
curl "http://localhost:7860/api/v1/monitor/transactions?flow_id=00000000-0000-0000-0000-000000000000"
# 3. Delete user messages by session without authentication
curl -X DELETE http://localhost:7860/api/v1/monitor/messages/session/00000000-0000-0000-0000-000000000000
```
Expected vs Actual Behavior:
- Expected: All requests should return
401 Unauthorized - Actual: All requests return successful responses with sensitive data or perform destructive operations
Impact
Vulnerability Type: Broken Authentication and Authorization (OWASP Top 10 - A01:2021)
Severity: High
Who is Impacted:
- All Langflow users: Personal conversation data exposed to unauthorized access
- System administrators: Transaction logs disclosed
Specific Impacts:
1. Data Breach: Unauthorized access to user conversations containing potentially sensitive personal information
2. Privacy Violation: Transaction histories and user activity patterns exposed without consent
3. Data Destruction: Malicious actors can delete user conversation histories without authorization
4. Compliance Risk: Potential violations of data protection regulations (GDPR, CCPA, etc.)
5. System Intelligence: Attackers can gather information about system usage patterns and user behavior
Attack Scenarios:
- Malicious users accessing proprietary conversation data
- Malicious users deleting other users' conversation histories
- Automated scraping of all user conversations for data harvesting
- Reconnaissance attacks to understand system architecture and usage patterns
Recommended Fix:
Add authentication dependencies to all affected endpoints:
```python
@router.get("/messages", dependencies=[Depends(get_current_active_user)])
@router.get("/transactions", dependencies=[Depends(get_current_active_user)])
@router.delete("/messages/session/{session_id}", dependencies=[Depends(get_current_active_user)])
```
Environment:
- Langflow Version: Current main branch
- Affected Components: API v1 monitoring endpoints
- Authentication System: FastAPI dependency injection with
get_current_active_user
<img width="1908" height="1029" alt="25-090901" src="https://github.com/user-attachments/assets/44bd03b4-6ada-45b7-b81b-9cb83747172b" />
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality high, integrity high, availability none.
Weakness class
CVE-2026-21445 is classified as CWE-306: Missing Authentication for Critical Function. A sensitive function can be reached without authenticating at all.
Affected software
CVE-2026-21445 is recorded against 2 packages.
- langflow (fixed in 1.7.1)
- langflow-base (fixed in 0.7.1)
Timeline and source
Published on 2 January 2026 and last revised on 13 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)
Details
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| langflow | — | 1.7.1 |
| langflow-base | — | 0.7.1 |
References
Similar Threats
- Medium CVE-2026-10128
- High CVE-2026-10129
- Critical CVE-2026-10134
- Critical CVE-2026-10140
- High CVE-2026-10546
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Exploit Protection
Are you running langflow?
CVE-2026-21445 carries CVSS 8.0 High rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.
Check My Site For CVE-2026-21445 →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.