# CVE-2026-114396: Trudesk through 1.2.11 MongoDB $where Injection via tickets search API


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/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-7g8w-325w-mwfp

## What is CVE-2026-114396?

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

### Official description

Trudesk through 1.2.11 contains a server-side JavaScript injection vulnerability that allows authenticated users to inject code into a MongoDB $where clause via the search parameter. Attackers can close the regular expression in GET /api/v1/tickets/search to loop mongod for denial of service or leak full ticket documents including internal notes.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-114396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114396 is a high-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-114396 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-114396/ (Markdown: https://insights.sbomify.com/CVE-2026-114396/index.md)
```

## Sources

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

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