GHSA-c5cp-vx83-jhqx — langflow-base
Fix: langflow-ai/langflow@3fed9feGHSA-c5cp-vx83-jhqx is a Missing Authentication vulnerability in langflow-base. EPSS puts its 30-day exploitation probability at 33.7% (98th percentile). A fix is available for langflow-base — see the affected versions and patch details below.
Langflow Missing Authentication on Critical API Endpoints
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-c5cp-vx83-jhqx.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
langflow-base🐍langflowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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:
-
GET
/api/v1/monitor/messages(Line 61)@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]: -
GET
/api/v1/monitor/transactions(Line 183)@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]: -
DELETE
/api/v1/monitor/messages/session/{session_id}(Line 165)@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:
@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:
- Start a Langflow server instance
- Ensure no authentication headers or API keys are provided
Reproduction Commands:
# 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:
- Data Breach: Unauthorized access to user conversations containing potentially sensitive personal information
- Privacy Violation: Transaction histories and user activity patterns exposed without consent
- Data Destruction: Malicious actors can delete user conversation histories without authorization
- Compliance Risk: Potential violations of data protection regulations (GDPR, CCPA, etc.)
- 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:
@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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | langflow-base | all versions | 0.7.1pip install --upgrade 'langflow-base==0.7.1' |
| 🐍PyPI | langflow | all versions | 1.7.1pip install --upgrade 'langflow==1.7.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update langflow-base to 0.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c5cp-vx83-jhqx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c5cp-vx83-jhqx can be triaged on real exposure rather than presence alone.
Tailored to GHSA-c5cp-vx83-jhqx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-c5cp-vx83-jhqx
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-c5cp-vx83-jhqx -u https://target- Template
- Langflow - Broken Access Control
- Severity
- critical
- Impact
- Unauthenticated attackers can access sensitive user data and perform destructive actions, risking data loss and privacy breaches.
- Remediation
- Update to version 1.7.0.dev45 or later.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-c5cp-vx83-jhqx in your dependencies?
O3 Security finds GHSA-c5cp-vx83-jhqx across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.