CVE-2026-121937
Received Received - Intake

LoonFlow Missing Authorization in TicketFlowHistoryView

Vulnerability report for CVE-2026-121937, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: VulnCheck

Description

loonflow before r3.2.3 contains a missing authorization vulnerability in TicketFlowHistoryView that allows any authenticated user to read other users' ticket flow history by supplying a ticket UUID. Attackers can request the ticket_flow_history endpoint, which skips ticket_view_permission_check, to obtain approval comments and processor names, emails and phone numbers.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-04
Last Modified
2026-11-04
Generated
2026-11-04
AI Q&A
2026-11-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
blackholll loonflow 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-121937 is an Insecure Direct Object Reference (IDOR) vulnerability in the loonflow ticket and workflow approval engine. It allows any authenticated non-admin user to read another user's ticket approval history and processor personally identifiable information (PII) by exploiting insufficient access controls in the ticket API. The vulnerability exists because the TicketFlowHistoryView endpoint fails to verify whether the requesting user has permission to view the specific ticket.

Detection Guidance

To detect this vulnerability, check if your loonflow instance is running a version before r3.2.3. Use commands like 'curl -s https://your-loonflow-instance.com/api/ticket_flow_history?ticket_id=SOME_UUID' with a valid ticket UUID. If the response includes sensitive data without proper authorization, the system is vulnerable.

Impact Analysis

Attackers can access sensitive information such as approval comments, processor names, emails, and phone numbers by supplying a ticket UUID. This compromises confidentiality by exposing PII and approval histories. The impact is limited to within the same tenant as queries filter by tenant ID.

Mitigation Strategies

Immediately upgrade loonflow to version r3.2.3 or later. Review and apply the patch in commit a6495b0c2ca9e5dede8e49217a0468bcfa946de4. Ensure all views enforce ticket_view_permission_check and restrict access to ticket flow history based on user permissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-121937. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...