Live › vulnerability › CVE-2026-114401
Go to dashboardTrudesk through 1.2.11 passes user-supplied regex patterns into its login lookup at POST /api/v1/login. An unauthenticated attacker can use patterns like (admin|root) or a.* and tell 'Invalid User' from 'Invalid Password' responses to discover valid account names.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any self-hosted Trudesk instance up to and including 1.2.11 with its login endpoint reachable is in scope, because the flaw is in the unauthenticated login route. Instances behind a network restriction that blocks the login endpoint from untrusted sources are less exposed. The sources do not name a patched version.
No product ranges from the sources yet.
1.2.11 is in the stated range.a.* to POST /api/v1/login and see whether the responses differ between existing and non-existing usernames.Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Trudesk through 1.2.11 contains a regular expression injection vulnerability that allows unauthenticated attackers to enumerate usernames by submitting regex patterns to POST /api/v1/login. Attackers can send alternations or prefixes like (admin|root) or a.* and distinguish 'Invalid User' from 'Invalid Password' responses to discover valid accounts.
This page as .md · .json · in your agent: get_signal("CVE-2026-114401")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.