GHSA-c5cp-vx83-jhqx: Pip/langflow vulnerability

Published Jan 2, 2026
·
Updated

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(getcurrentactiveuser)] authentication dependency:

Affected Endpoints:

1. GET /api/v1/monitor/messages (Line 61) python @router.get("/messages") # ❌ Missing authentication async def getmessages( session: DbSession, flowid: Annotated[UUID | None, Query()] = None, sessionid: 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 gettransactions( flowid: Annotated[UUID, Query()], session: DbSession, params: Annotated[Params | None, Depends(customparams)], ) -> Page[TransactionTable]:

3. DELETE /api/v1/monitor/messages/session/{sessionid} (Line 165) python @router.delete("/messages/session/{sessionid}", statuscode=204) # ❌ Missing authentication async def deletemessagessession( sessionid: str, session: DbSession, ):

Inconsistency Evidence: Other endpoints in the same file properly implement authentication: python @router.get("/messages/sessions", dependencies=[Depends(getcurrentactiveuser)]) # ✅ Properly secured @router.delete("/messages", statuscode=204, dependencies=[Depends(getcurrentactiveuser)]) # ✅ 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?flowid=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(getcurrentactiveuser)]) @router.get("/transactions", dependencies=[Depends(getcurrentactiveuser)]) @router.delete("/messages/session/{sessionid}", dependencies=[Depends(getcurrentactiveuser)])

Environment: - Langflow Version: Current main branch - Affected Components: API v1 monitoring endpoints - Authentication System: FastAPI dependency injection with getcurrentactiveuser

<img width="1908" height="1029" alt="25-090901" src="https://github.com/user-attachments/assets/44bd03b4-6ada-45b7-b81b-9cb83747172b" />

Affected Software

2 affected componentsFixes available
pip/langflow<=1.7.0.dev44
1.7.1
pip/langflow-base<=0.6.9
0.7.1

Event History

Jan 2, 2026
Advisory Published
via GitHub·09:11 PM
Data Sourced
via GitHub·09:11 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of GHSA-c5cp-vx83-jhqx?

GHSA-c5cp-vx83-jhqx is classified as a critical vulnerability due to its lack of authentication controls on multiple API endpoints.

2

How do I fix GHSA-c5cp-vx83-jhqx?

To resolve GHSA-c5cp-vx83-jhqx, update Langflow to version 1.5.1 or later.

3

What data is at risk due to GHSA-c5cp-vx83-jhqx?

GHSA-c5cp-vx83-jhqx exposes sensitive user conversation data and transaction histories due to unauthenticated access.

4

Which versions of Langflow are affected by GHSA-c5cp-vx83-jhqx?

Langflow versions prior to 1.5.1 are affected by GHSA-c5cp-vx83-jhqx.

5

What operations can be performed by unauthenticated users in GHSA-c5cp-vx83-jhqx?

Unauthenticated users can perform destructive operations, including message deletion, due to GHSA-c5cp-vx83-jhqx.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203