PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-114392 polonel CVE debrief

CVE-2026-114392 is an authorization bypass vulnerability in Trudesk through 1.2.11 that allows authenticated users to read tickets outside their groups via GET /api/v1/tickets/:uid. Attackers can enumerate sequential ticket uids to read every ticket's subject, issue, comments, owner and assignee. This vulnerability has a medium severity and defenders should assess exposure and prioritize verification of ticket reading access controls. The CVE record and NVD entry provide details on the authorization bypass vulnerability in Trudesk.

Vendor
polonel
Product
trudesk
CVSS
MEDIUM 6.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-21
Original CVE updated
2026-10-27
Advisory published
2026-10-21
Advisory updated
2026-10-27

Who should care

Defenders responsible for Trudesk instances, particularly those with authenticated user access, should assess exposure and prioritize verification of ticket reading access controls.

Why it matters

CVE-2026-114392 is a medium-severity authorization bypass vulnerability in Trudesk that allows authenticated users to read tickets outside their groups. Defenders should prioritize verifying exposure, assessing potential for ticket enumeration attacks, and updating access controls to prevent unauthorized ticket reading.

  • Authenticated users may be able to read sensitive ticket information outside their groups
  • Enumeration of ticket UIDs could lead to unauthorized access to ticket data
  • Defenders need to verify exposure and update access controls to prevent unauthorized ticket reading
  • Remediation priority is high for Trudesk instances with high volumes of ticket activity

Technical summary

The Trudesk application through version 1.2.11 contains an authorization bypass vulnerability. This vulnerability allows authenticated users to read tickets outside their groups by making a GET request to /api/v1/tickets/:uid. An attacker can exploit this by enumerating sequential ticket UIDs to access the subject, issue, comments, owner, and assignee of every ticket. The CVE record and NVD entry provide details on the authorization bypass vulnerability in Trudesk. Defenders should prioritize verifying exposure of Trudesk instances to authenticated users and assessing the potential for ticket enumeration attacks.

Defensive priority

Defenders should prioritize verifying exposure of Trudesk instances to authenticated users and assessing the potential for ticket enumeration attacks.

Recommended defensive actions

  • Verify Trudesk instance exposure to authenticated users
  • Assess potential for ticket enumeration attacks
  • Review and update access controls for ticket reading
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the authorization bypass vulnerability in Trudesk. However, the corpus does not establish versions beyond 1.2.11, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-114392 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-114392

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-114392 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-114392

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.