# CVE-2026-114393: Trudesk authorization bypass in ticket API

Source: https://junglewise.ai/threats/cve-2026-114393-trudesk-through-1-2-11-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-21. Updated: 2026-10-21  
License: CC BY 4.0 with a link back

CVE-2026-114393 · Severity: medium · CVSS 4.3 · Published 2026-10-21

Trudesk is an open-source help desk ticketing system that manages customer support requests. An authenticated user can modify or mass-close support tickets assigned to other groups by directly specifying ticket IDs in API requests, circumventing group-based access controls. An attacker with any user account can disrupt ticket management, alter ticket status, or reassign cases across organizational boundaries.

Technologies: [Polonel Trudesk](https://junglewise.ai/threats/technologies/trudesk). Vendors: [Polonel](https://junglewise.ai/threats/vendors/polonel).

## Quick answers

**Is CVE-2026-114393 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-114393 being exploited in the wild.

**How severe is CVE-2026-114393?** Medium severity, with a CVSS score of 4.3, published 21 October 2026.

**Which products and versions are affected?** Polonel Trudesk through 1.2.11.

**Is there a fix for CVE-2026-114393?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-114393 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-114393?** Check whether you run Polonel Trudesk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in the PUT /api/v1/tickets/:id and PUT /api/v2/tickets/batch endpoints, which fail to enforce group membership authorization when processing ticket updates. The API only checks for the generic tickets:update role permission but does not verify that the authenticated user belongs to the group owning the target ticket. An attacker can supply arbitrary ticket ObjectIds to modify status, subject, group, priority, or assignee fields, or perform bulk ticket closure operations.

## Affected products

- polonel Trudesk through 1.2.11

## Timeline

- 2026-10-21: disclosed

## References

- [https://github.com/polonel/trudesk](https://github.com/polonel/trudesk)
- [https://github.com/polonel/trudesk/blob/v1.2.11/src/controllers/api/v1/tickets.js](https://github.com/polonel/trudesk/blob/v1.2.11/src/controllers/api/v1/tickets.js)

## Related threats

- [Trudesk path traversal and authorization bypass in avatar upload](https://junglewise.ai/threats/cve-2026-114402-trudesk-through-1-2-11-contains-a-path-traversal-and)
- [Trudesk missing authentication in ticket attachments](https://junglewise.ai/threats/cve-2026-114400-trudesk-through-1-2-11-contains-a-missing-authentication)
- [Trudesk unrestricted file upload to stored XSS](https://junglewise.ai/threats/cve-2026-114398-trudesk-through-1-2-11-contains-an-unrestricted-file-upload)
- [Trudesk missing authentication in debug routes](https://junglewise.ai/threats/cve-2026-114397-trudesk-through-1-2-11-contains-a-missing-authentication)
- [Trudesk server-side JavaScript injection in ticket search](https://junglewise.ai/threats/cve-2026-114396-trudesk-through-1-2-11-contains-a-server-side-javascript)