# CVE-2026-114394: Trudesk authorization bypass in comments and tickets

Source: https://junglewise.ai/threats/cve-2026-114394-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-114394 · Severity: medium · CVSS 4.3 · Published 2026-10-21

Trudesk is an open-source help desk and ticketing system. An authenticated user can forge comments, internal notes, and tickets under any other user's identity by manipulating user ID fields, potentially allowing attackers to impersonate administrators and create misleading audit trails or issue false tickets on behalf of others.

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

## Quick answers

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

**How severe is CVE-2026-114394?** 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-114394?** 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-114394 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-114394?** 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

An authorization bypass vulnerability in the Trudesk ticket API allows authenticated users to post comments, internal notes, and create tickets with arbitrary owner IDs via user-controlled ownerId or owner parameters in API requests. The vulnerability affects postComment, postInternalNote, and ticket creation endpoints, enabling unauthorized attribute forgery without proper ownership validation. No privilege escalation is required; authentication alone is sufficient to abuse the flaw.

## 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)