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-114400 Overview
CVE-2026-114400 is a missing authentication vulnerability in Trudesk through version 1.2.11, an open-source help desk and ticketing application. The flaw allows unauthenticated attackers to download private ticket attachments served from the /uploads directory. The root cause is middleware ordering: express.static serves the public/ directory before the hasAuth-guarded /uploads mount is evaluated. Attackers who know or guess a ticket ObjectId and filename can retrieve confidential attachments without credentials. The weakness maps to CWE-552: Files or Directories Accessible to External Parties.
Critical Impact
Unauthenticated remote attackers can exfiltrate confidential ticket attachments, including customer data, credentials, and internal documentation uploaded to Trudesk.
Affected Products
- Trudesk versions up to and including 1.2.11
- Deployments exposing the Trudesk HTTP interface to untrusted networks
- Self-hosted instances running the vulnerable src/middleware/index.js configuration
Discovery Timeline
- 2026-10-21 - CVE-2026-114400 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114400
Vulnerability Analysis
Trudesk uses the Express.js framework and registers middleware in src/middleware/index.js. The application mounts express.static against the public/ directory earlier in the middleware chain than the authentication-guarded /uploads route. Because Express evaluates middleware in registration order, static file resolution occurs before the hasAuth function has a chance to reject the request. As a result, any HTTP GET to a path under /uploads/ that resolves to an existing file on disk is served directly to the caller.
Ticket attachments are stored under predictable paths that incorporate the ticket's MongoDB ObjectId and the original filename. An attacker who obtains or guesses these values can request the attachment URL and receive the file content with no session cookie, token, or API key.
Root Cause
The defect is a middleware registration order issue combined with missing path-level authorization on the static file handler. The hasAuth guard is applied to a later /uploads mount, but the earlier express.static('public') handler intercepts matching requests first. Trudesk relies on obscurity of the ObjectId and filename rather than enforcing an authorization check on each file read.
Attack Vector
Exploitation requires only network access to the Trudesk web interface. The attacker crafts a request such as GET /uploads/<ticketObjectId>/<filename> and receives the attachment body in the response. ObjectId values are 24-character hex strings that encode a timestamp, machine identifier, process ID, and counter, making targeted guessing feasible when some fields are known or leaked through other channels such as email notifications, log files, or referrer headers.
See the HackMD Trudesk Vulnerability Report and the VulnCheck Trudesk Security Advisory for the vulnerable code paths at src/middleware/index.js lines 59-65 and line 140.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114400
Indicators of Compromise
- Unauthenticated HTTP GET requests to /uploads/<objectid>/<filename> returning HTTP 200 with non-empty bodies
- Access log entries for /uploads paths without an associated authenticated session cookie
- Spikes in sequential or enumerated ObjectId values appearing in access logs within short time windows
- Downloads of attachments from IP addresses or user agents that have never authenticated to Trudesk
Detection Strategies
- Parse Trudesk and reverse proxy access logs for /uploads/ requests and correlate against the authenticated session store to identify unauthorized downloads
- Deploy a web application firewall rule that requires a valid session cookie or bearer token on any request matching /uploads/*
- Alert on anomalous volumetric access to the /uploads path from a single source address
Monitoring Recommendations
- Enable verbose HTTP access logging on the Trudesk host and forward logs to a central analytics platform
- Monitor response sizes on /uploads endpoints to identify bulk exfiltration attempts
- Review historical logs for prior unauthenticated access to /uploads to assess whether exploitation has already occurred
How to Mitigate CVE-2026-114400
Immediate Actions Required
- Restrict network exposure of the Trudesk interface to trusted networks or require VPN access until a vendor patch is available
- Place an authenticating reverse proxy, such as nginx with auth_request, in front of Trudesk to enforce authentication on /uploads/* before requests reach the application
- Audit access logs for prior unauthenticated requests to /uploads and notify affected ticket owners if sensitive attachments were exposed
- Rotate any credentials, API keys, or secrets that may have been shared via Trudesk ticket attachments
Patch Information
At the time of publication, no fixed version is referenced in the NVD entry for CVE-2026-114400. Monitor the Trudesk GitHub repository for a release that reorders middleware so that hasAuth is applied before express.static resolves /uploads paths, or that moves ticket attachments outside of any statically served directory.
Workarounds
- Reconfigure the deployment so that express.static does not serve the public/ directory on paths overlapping with /uploads
- Move ticket attachment storage to a location outside the statically served directory and serve files only through an authenticated route handler
- Enforce /uploads/* authentication at the reverse proxy layer using session validation or mTLS
- Apply strict IP allowlisting on the /uploads path when the application is exposed to the internet
# nginx reverse proxy workaround: require authenticated session for /uploads
location /uploads/ {
auth_request /auth-check;
proxy_pass http://trudesk_backend;
}
location = /auth-check {
internal;
proxy_pass http://trudesk_backend/api/v1/users/session;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-URI $request_uri;
}
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

