Skip to main content
Vulnerability Database/CVE-2026-114396

CVE-2026-114396: Trudesk SSRF Vulnerability

CVE-2026-114396 is a server-side request forgery vulnerability in Trudesk that enables authenticated attackers to inject malicious code into MongoDB queries. This post covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114396 Overview

CVE-2026-114396 is a server-side JavaScript injection vulnerability in Trudesk through version 1.2.11, an open-source help desk and ticketing platform. The flaw resides in the ticket search API endpoint GET /api/v1/tickets/search, where user-supplied input flows into a MongoDB $where clause without proper sanitization. Authenticated users can close the regular expression used by the server and inject arbitrary JavaScript executed by mongod. Successful exploitation enables denial of service through infinite loops or disclosure of full ticket documents, including internal notes that should remain restricted. The vulnerability is classified under CWE-943: Improper Neutralization of Special Elements in Data Query Logic.

Critical Impact

Authenticated attackers can execute arbitrary JavaScript inside the MongoDB server process, causing denial of service or exfiltrating sensitive ticket data including internal notes.

Affected Products

  • Trudesk through version 1.2.11
  • Deployments exposing the /api/v1/tickets/search endpoint to authenticated users
  • MongoDB backends evaluating $where clauses constructed from the Trudesk ticket model

Discovery Timeline

  • 2026-10-21 - CVE-2026-114396 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114396

Vulnerability Analysis

Trudesk builds a MongoDB query for ticket search by embedding the user-supplied search parameter inside a $where clause, as implemented in the ticket model. The server concatenates the parameter into a JavaScript regular expression literal evaluated server-side by mongod. Because the input is not escaped, an attacker can terminate the regex and append arbitrary JavaScript. The injected code runs inside the database process with the privileges of the Trudesk service account. The vulnerability requires low-privilege authentication but no user interaction. Impact ranges from availability loss through CPU-bound loops to confidentiality loss by overriding predicate logic and returning tickets the caller should not see.

Root Cause

The root cause is unsafe construction of a $where predicate from untrusted input. MongoDB evaluates $where as JavaScript, so any character that breaks out of the surrounding regex delimiter yields code execution within the query engine. The code path does not validate the search term against an allowlist, escape regex metacharacters, or switch to a safer operator such as $regex with a pre-compiled pattern. See the VulnCheck advisory for the full technical write-up.

Attack Vector

An authenticated user sends a crafted search query string to GET /api/v1/tickets/search. The payload closes the regular expression and introduces a JavaScript expression evaluated by MongoDB. For denial of service, the payload invokes a non-terminating loop that consumes mongod worker threads. For data disclosure, the payload substitutes a predicate that returns true for every document, causing the API to return all ticket records including internal notes. Additional details are documented in the HackMD write-up.

No verified proof-of-concept code is included here. Refer to the linked advisories for sanitized payload examples.

Detection Methods for CVE-2026-114396

Indicators of Compromise

  • Requests to /api/v1/tickets/search containing regex delimiter characters followed by JavaScript tokens such as while, function, return, or sleep.
  • Sustained high CPU usage by the mongod process correlated with specific authenticated sessions.
  • Unusually large response payloads from the ticket search endpoint that return records beyond the caller's typical scope.
  • Repeated 5xx errors or timeouts on the ticket search endpoint following suspicious search parameter values.

Detection Strategies

  • Inspect web server and reverse proxy logs for search query parameters containing /, ;, //, or encoded forms of JavaScript operators.
  • Enable MongoDB profiling to capture slow $where operations and correlate them with the Trudesk application user.
  • Deploy a WAF rule that blocks regex-breakout patterns on the /api/v1/tickets/search route.

Monitoring Recommendations

  • Alert on authenticated API callers whose request-to-response byte ratio deviates sharply from baseline on the search endpoint.
  • Track mongod CPU, operation duration, and connection saturation metrics with alerts tied to the Trudesk database.
  • Audit ticket-read activity for accounts accessing tickets outside their assigned groups or departments.

How to Mitigate CVE-2026-114396

Immediate Actions Required

  • Restrict network access to the Trudesk ticket search endpoint to trusted internal users while a fix is evaluated.
  • Rotate credentials for any accounts that may have been used to probe or exploit the endpoint.
  • Review MongoDB audit logs for $where evaluations originating from the Trudesk application and investigate anomalies.
  • Disable server-side JavaScript evaluation in MongoDB where business logic allows by starting mongod with --noscripting.

Patch Information

No vendor patch is referenced in the NVD entry at publication time. All Trudesk releases through 1.2.11 are affected. Monitor the Trudesk GitHub repository and the VulnCheck advisory for a fixed release and apply it as soon as it is available.

Workarounds

  • Place the Trudesk API behind a reverse proxy that rejects search parameters containing regex metacharacters or JavaScript keywords.
  • Run MongoDB with server-side scripting disabled using the --noscripting flag to neutralize $where evaluation.
  • Enforce least privilege on the MongoDB user used by Trudesk so that compromise cannot pivot to other databases.
  • Limit the ticket search feature to specific roles until a patched version is deployed.
bash
# Disable MongoDB server-side JavaScript to neutralize $where injection
mongod --noscripting --config /etc/mongod.conf

# Example nginx rule to block regex-breakout characters on the search endpoint
location /api/v1/tickets/search {
    if ($arg_search ~* "[/;]|function|while|return|sleep") {
        return 400;
    }
    proxy_pass http://trudesk_upstream;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.