# CVE-2026-114394: Trudesk through 1.2.11 Authorization Bypass via Ticket Comment and Create APIs


- **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:** 21 Oct 2026
- **Also known as:** GHSA-x3mr-67c9-5xq8

## What is CVE-2026-114394?

CVE-2026-114394 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 authenticated users to post content attributed to other users by supplying user-controlled owner IDs. Attackers can set ownerId or owner in postComment, postInternalNote, and ticket create requests to forge administrator-authored comments, internal notes, and tickets on any ticket.

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

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


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

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

## Is CVE-2026-114394 being exploited?

There is no known exploitation of CVE-2026-114394 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114394 is a medium-severity vulnerability in polonel trudesk, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114394 in the wild and no public exploit code.

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-114394/ (Markdown: https://insights.sbomify.com/CVE-2026-114394/index.md)
```

## Sources

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

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