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.
Published: 2026-11-04
Score: 2.3 Low
EPSS: n/a
KEV: No
Impact: Unauthorized Data Disclosure
Action: Apply Patch
AI Analysis

Impact

The vulnerability is a missing authorization check in the TicketFlowHistoryView of loonflow, allowing any authenticated user to request the ticket_flow_history endpoint for a ticket UUID that owns no privileges over. The endpoint returns the ticket’s flow history, including approval comments, processor names, emails, and phone numbers, which constitutes a privacy breach for other users’ personal and sensitive data.

Affected Systems

The affected product is blackholll’s loonflow. Any deployment running a version before r3.2.3 is vulnerable; the issue was resolved starting in r3.2.3, so all releases older than that should be considered affected.

Risk and Exploitability

The CVSS score of 2.3 indicates a low risk of exploitation compared to other vulnerabilities. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, reducing the perceived urgency. However, any authenticated user—who may already have access to the system—can exploit the flaw, so the attack vector requires only legitimate credentials but not elevated privileges. The overall exposure is limited to data confidentiality breaches rather than system compromise.

Generated by OpenCVE AI on November 4, 2026 at 13:33 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade loonflow to version r3.2.3 or later to obtain the Fixed TicketFlowHistoryView authorization check.
  • If an upgrade is not immediately possible, restrict access to the /ticket_flow_history endpoint by modifying the web server or reverse proxy configuration to allow only users with the required role or ticket ownership.
  • Implement monitoring of the /ticket_flow_history endpoint usage to detect anomalous access patterns from users who do not own the ticket, and apply alerts or blocklists accordingly.

Generated by OpenCVE AI on November 4, 2026 at 13:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 04 Nov 2026 12:45:00 +0000

Type Values Removed Values Added
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.
Title loonflow before r3.2.3 IDOR via ticket_flow_history Endpoint
First Time appeared Loonflow Project
Loonflow Project loonflow
Weaknesses CWE-639
CPEs cpe:2.3:a:loonflow_project:loonflow:*:*:*:*:*:*:*:*
Vendors & Products Loonflow Project
Loonflow Project loonflow
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Loonflow Project Loonflow
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-11-04T12:31:17.088Z

Reserved: 2026-11-04T12:05:48.820Z

Link: CVE-2026-121937

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-04T13:17:27.870

Modified: 2026-11-04T13:17:27.870

Link: CVE-2026-121937

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-04T13:45:14Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key