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-110256 Overview
CVE-2026-110256 is an LDAP injection vulnerability in Finsys Dockhand through version 1.0.18. The flaw resides in the tryLdapAuth function within src/lib/server/auth.ts. The code inserts the login username into the LDAP search filter without escaping wildcard characters. Unauthenticated attackers can send wildcard patterns such as a* to /api/auth/login and measure response timing to enumerate valid Lightweight Directory Access Protocol (LDAP) usernames. The attack also bypasses per-username rate limiting because each probe matches multiple accounts. The issue is tracked under [CWE-90] (Improper Neutralization of Special Elements used in an LDAP Query).
Critical Impact
Unauthenticated remote attackers can enumerate valid LDAP usernames from the authentication endpoint, enabling targeted credential attacks against downstream directory services.
Affected Products
- Finsys Dockhand versions through 1.0.18
- Deployments using the tryLdapAuth authentication path
- Dockhand instances with the /api/auth/login endpoint exposed to untrusted networks
Discovery Timeline
- 2026-10-13 - CVE-2026-110256 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-110256
Vulnerability Analysis
The vulnerability exists in the tryLdapAuth function in src/lib/server/auth.ts. The function constructs an LDAP search filter by concatenating the user-supplied username parameter directly into the filter string. LDAP special characters, including the * wildcard, are not escaped before insertion.
An attacker submitting a* as the username causes the LDAP server to match every account whose username starts with the letter a. The server takes measurably longer to process matches that return results than to process filters with no match. By comparing response times across incremental prefixes, an attacker reconstructs valid usernames character by character.
Because each probe is a different wildcard pattern rather than a specific username, per-username rate limiting fails to block the enumeration. The attack succeeds without authentication and leaves no failed-login records tied to specific accounts.
Root Cause
The root cause is missing input sanitization before LDAP filter construction. The tryLdapAuth function does not call an LDAP escape routine on the username field. LDAP metacharacters such as *, (, ), \, and NUL must be escaped per RFC 4515 to prevent filter manipulation.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker sends crafted POST requests to /api/auth/login containing wildcard patterns in the username field. The attacker measures server response timing to infer which patterns match existing directory entries. The vulnerability mechanism and response differentials are documented in the GitHub Security Advisory and the VulnCheck Advisory.
Detection Methods for CVE-2026-110256
Indicators of Compromise
- Repeated POST requests to /api/auth/login where the username field contains LDAP wildcard characters such as *, (, or )
- Sequential login attempts with incremental prefix patterns (a*, ab*, abc*) from a single source
- Unusually high request volume to the authentication endpoint without corresponding account lockouts
- Timing-based probing patterns with sub-second intervals from automated clients
Detection Strategies
- Deploy web application firewall rules that reject login payloads containing unescaped LDAP metacharacters
- Correlate authentication endpoint traffic to identify enumeration patterns across source IPs and User-Agent strings
- Alert on login requests where the username field length or character set deviates from organizational naming conventions
Monitoring Recommendations
- Enable verbose logging on the Dockhand application and forward authentication events to a central SIEM
- Monitor LDAP server query logs for filter strings containing wildcard expressions originating from the Dockhand service account
- Track response time distributions on /api/auth/login for statistical anomalies indicating timing-based probing
How to Mitigate CVE-2026-110256
Immediate Actions Required
- Upgrade Finsys Dockhand to version 1.0.19 or later, which addresses the LDAP injection flaw
- Restrict network access to /api/auth/login to trusted networks or behind a reverse proxy with input filtering
- Audit LDAP directory logs for prior enumeration activity targeting the Dockhand service account
Patch Information
Finsys released a fix in Dockhand 1.0.19. The patched release escapes LDAP metacharacters in user-supplied input before filter construction. Review the GitHub Security Advisory GHSA-vmm5-cjvh-7vmv for release notes and upgrade guidance.
Workarounds
- Implement an upstream reverse-proxy rule to reject login requests whose username field contains *, (, ), \, or NUL bytes
- Enforce global rate limiting on /api/auth/login based on source IP in addition to per-username limits
- Restrict the Dockhand LDAP bind account to the minimum directory subtree required for authentication
# Example nginx rule to block LDAP metacharacters in login requests
location = /api/auth/login {
if ($request_body ~* "[\*\(\)\\]") {
return 400;
}
proxy_pass http://dockhand_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

