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

CVE-2026-114401: Trudesk Username Enumeration Vulnerability

CVE-2026-114401 is a regular expression injection flaw in Trudesk that enables unauthenticated attackers to enumerate valid usernames through the login API. This article covers technical details, affected versions, and mitigation.

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-114401 Overview

CVE-2026-114401 is a regular expression injection vulnerability in Trudesk through version 1.2.11, an open-source help desk and ticketing platform. The flaw resides in the POST /api/v1/login endpoint, which passes user-supplied input directly into a MongoDB query as a regex pattern. Unauthenticated attackers can submit crafted regex patterns such as (admin|root) or a.* and distinguish Invalid User from Invalid Password responses. This behavior enables systematic enumeration of valid usernames without any authentication. The weakness is tracked as CWE-943: Improper Neutralization of Special Elements in Data Query Logic.

Critical Impact

Unauthenticated remote attackers can enumerate valid Trudesk user accounts, enabling targeted credential stuffing, password spraying, and phishing campaigns against discovered users.

Affected Products

  • Trudesk versions up to and including 1.2.11
  • Trudesk POST /api/v1/login API endpoint
  • Deployments exposing the Trudesk login API to untrusted networks

Discovery Timeline

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

Technical Details for CVE-2026-114401

Vulnerability Analysis

Trudesk's authentication flow queries MongoDB for a user record matching the submitted username before validating the password. The username parameter received by POST /api/v1/login is forwarded into a query that treats the value as a regular expression rather than a literal string. When no account matches, the server returns Invalid User; when an account matches but the password check fails, the server returns Invalid Password. This response differential turns the login endpoint into an oracle for account existence.

An attacker can submit progressively narrower regex patterns to confirm whether users starting with specific prefixes exist. Alternation patterns such as (admin|root|support) allow bulk testing of common administrative usernames in a single request. The vulnerability requires no credentials, no user interaction, and operates entirely over the network.

Root Cause

The underlying issue is unsanitized user input flowing into a MongoDB regex query within the login controller. Relevant code paths are visible in common.js and user.js. The application fails to escape regex metacharacters or anchor the pattern, and it discloses distinct error messages for missing users versus incorrect passwords.

Attack Vector

Exploitation requires only HTTP access to the Trudesk login endpoint. An attacker sends a POST request with a JSON body containing a regex-crafted username field such as ^admin or (root|administrator|support) and a dummy password. By parsing which error message the server returns, the attacker confirms account existence. Repeated queries, scripted against a wordlist, allow comprehensive username harvesting. For a detailed walkthrough see the HackMD Vulnerability Analysis and the VulnCheck Security Advisory.

Detection Methods for CVE-2026-114401

Indicators of Compromise

  • Repeated POST /api/v1/login requests from a single source containing regex metacharacters such as ^, $, .*, |, or parentheses in the username field.
  • High-volume login requests returning Invalid User responses followed by narrower queries returning Invalid Password.
  • Login attempts whose username field length or character set deviates from legitimate account naming conventions.

Detection Strategies

  • Inspect application and reverse-proxy logs for login request bodies containing regex syntax tokens in the username parameter.
  • Correlate the ratio of Invalid User to Invalid Password responses per source IP; enumeration campaigns produce distinctive patterns.
  • Deploy web application firewall rules that flag or block login requests containing unescaped regex metacharacters.

Monitoring Recommendations

  • Alert on sustained unauthenticated requests to /api/v1/login from a single IP exceeding normal baselines.
  • Monitor for login traffic originating from anonymizing infrastructure, cloud ranges, or known scanner ASNs.
  • Capture full request bodies for login endpoints to retain evidence of regex payload submissions for incident response.

How to Mitigate CVE-2026-114401

Immediate Actions Required

  • Restrict access to the Trudesk /api/v1/login endpoint using network ACLs, VPN, or reverse-proxy allow-lists until a patched release is deployed.
  • Deploy a WAF rule rejecting login requests whose username field contains regex metacharacters.
  • Enforce account lockout and rate limiting on failed login attempts at the proxy or load balancer tier.

Patch Information

No fixed version is listed in the enriched advisory data at the time of publication. Monitor the Trudesk GitHub repository and the VulnCheck Security Advisory for a maintainer-supplied fix. Mitigation requires sanitizing the username input to treat it as a literal string and returning a single, uniform error message for all failed authentication attempts.

Workarounds

  • Patch the application locally to escape regex metacharacters in the username before constructing the MongoDB query, or convert the query to an exact string match.
  • Normalize authentication error responses so Invalid User and Invalid Password return identical messages and HTTP status codes.
  • Place the Trudesk instance behind an authenticating reverse proxy to prevent unauthenticated access to the login API from the public internet.
bash
# Example reverse-proxy filter rejecting regex metacharacters in the username field
# NGINX snippet - adjust to your deployment
location = /api/v1/login {
    if ($request_body ~* "\"username\"\s*:\s*\"[^\"]*[\.\*\+\?\|\(\)\[\]\^\$\\]") {
        return 400;
    }
    proxy_pass http://trudesk_backend;
}

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.