CVE-2026-121937 loonflow before r3.2.3 IDOR via ticket_flow_history Endpoint
Low 2.3
Published
Updated
Check this codebase for CVE-2026-121937 and fix it if it is affected.
What it is: CVE-2026-121937 is a low-severity vulnerability in blackholll loonflow, published on 4 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121937 exists.
Affected product: blackholll loonflow. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-121937/ (Markdown: https://insights.sbomify.com/CVE-2026-121937/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-121937?
CVE-2026-121937 is a low-severity vulnerability in blackholll loonflow, published on 4 Nov 2026.
Official 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.
Weakness: CWE-639
Which versions are affected by CVE-2026-121937?
How do I fix CVE-2026-121937?
No fix has been published for CVE-2026-121937 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-121937 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121937 exists.
Sources
Also known as GHSA-9h6j-f6mw-p7qh.