# CVE-2026-114393: Trudesk through 1.2.11 Authorization Bypass via Ticket Update API Endpoints


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-hqv6-jg73-3gmv

## What is CVE-2026-114393?

CVE-2026-114393 is a medium-severity vulnerability in polonel trudesk, published on 21 Oct 2026. 

### Official description

Trudesk through 1.2.11 contains an authorization bypass vulnerability that allows any authenticated user to modify tickets outside their groups via PUT /api/v1/tickets/:id and PUT /api/v2/tickets/batch. Attackers can supply arbitrary ticket ObjectIds to change status, subject, group, priority or assignee, or mass-close tickets, since only the default tickets:update role grant is checked.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-114393?


## How do I fix CVE-2026-114393?

No fix has been published for CVE-2026-114393 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114393 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114393 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114393 and fix it if it is affected.

What it is: CVE-2026-114393 is a medium-severity vulnerability in polonel trudesk, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114393 exists.

Affected product: polonel trudesk. 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-114393/ (Markdown: https://insights.sbomify.com/CVE-2026-114393/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114393
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114393
- OSV: https://osv.dev/vulnerability/CVE-2026-114393

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114393/
Summaries are generated and may contain mistakes; the official description above is the record.