Skip to content

CVE-2026-119744: Cendio ThinLinc Linux Remote Desktop Server Authentication Bypass via Web Access Multi-Step Login Logic

Density:
C-Level Executive Briefing CVE-2026-119744 CRITICAL SCORE 92/100

A critical improper authentication vulnerability affecting Cendio ThinLinc Linux Remote Desktop Server (versions 4.1.0 through 4.20.0) enables unauthenticated remote attackers to bypass identity verification and impersonate arbitrary system accounts, including root. Cataloged as weaponized by VulnCheck, the vulnerability resides within the browser-based client daemon (tlwebaccess), which exposes HTML5 and WebSocket VDI sessions over HTTPS. During multi-step authentication sequencesโ€”such as secondary one-time password (OTP) prompts, mandatory legal banners, or expired password dialogsโ€”the tlwebaccess session handler fails to cryptographically bind subsequent challenge responses to the initially initiated PAM transaction context. By manipulating session state tokens across transition boundaries, an attacker can substitute target user identities and obtain an active VNC/SSH session as root. Because ThinLinc gateways sit on enterprise perimeters bridging external traffic into private compute clusters, Hermes evaluates this vulnerability at HTS 92 (CRITICAL).

HYBRID

HERMES THREAT SCORE & PERIMETER VDI AUTHENTICATION INTEGRITY EVALUATION

Target: ThinLinc Web Access Session Manager (tlwebaccess / PAM Multi-Step Auth)
Confidence: 97%
92 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 19 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 16 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

[object Object]

Cendio ThinLinc is an enterprise Linux remote desktop and Virtual Desktop Infrastructure (VDI) platform built on open-source standards including TigerVNC, noVNC, PulseAudio, and OpenSSH. ThinLinc provides high-performance graphical desktop access to Linux server farms, supercomputing centers, university engineering departments, and enterprise developer workstations.

At the architectural core of ThinLincโ€™s remote access surface sits ThinLinc Web Access (tlwebaccess), a daemon listening on TCP port 300 (or port 3001) that serves a browser-based HTML5 VNC client. tlwebaccess acts as an intermediary authentication gateway between the userโ€™s web browser and the internal ThinLinc Master service (vsmserver). Upon successful authentication, vsmserver selects an agent host running vsmagent and establishes a secure virtual desktop session.

+-------------------------------------------------------------------------+
| Untrusted External Attacker (Browser Client) |
+-------------------------------------------------------------------------+
|
| 1. POST /login (Initiates OTP/Banner flow)
| 2. Intercept & rewrite session state
v
+---------------------------------------+
| Cendio ThinLinc Web Access Gateway |
| (tlwebaccess.service on TCP 300/3001) |
+---------------------------------------+
|
| 3. Desynchronized PAM Handle validation
v
+---------------------------------------+
| ThinLinc Master Daemon (vsmserver) |
| Spawns VNC/SSH session as ROOT |
+---------------------------------------+
|
| 4. Full Root Interactive Desktop
v
+---------------------------------------+
| Internal Enterprise Compute Subnet |
+---------------------------------------+

To support enterprise identity architectures, ThinLinc integrates with Linux Pluggable Authentication Modules (PAM), accommodating multi-factor authentication (MFA/OTP), Kerberos, LDAP, Active Directory, password change prompts, and custom legal disclaimer banners. In tlwebaccess versions 4.1.0 through 4.20.0, a state machine logic vulnerability allows an attacker to desynchronize the ongoing multi-step authentication process, forcing the backend daemon to finalize the login sequence under the identity of root or another privileged user.

The vulnerability resides in the session transition handler of tlwebaccess, which manages state across HTTP POST requests during conversational PAM exchanges.

When a multi-step PAM module is invoked (such as pam_google_authenticator.so for OTP, or pam_issue.so / pam_motd.so for mandatory acknowledgment banners), tlwebaccess returns an intermediary challenge to the browser client. The client answers this secondary prompt via an additional HTTP request.

In vulnerable releases of tlwebaccess, the intermediate state object stored in the HTTP session cache failed to enforce immutability on the authenticated username. Consider the following conceptual decomposition of the vulnerable session processing loop:

# Conceptual representation of vulnerable session handling in tlwebaccess
class WebLoginHandler:
def handle_multistep_response(self, request):
session_id = request.get_cookie("TL_SESSION_ID")
session = session_store.get(session_id)
if not session or session.state != STATE_PAM_CONVERSATION:
return self.render_error("Invalid session state")
# VULNERABILITY: Client-supplied username parameter accepted during challenge response
submitted_user = request.get_param("username")
if submitted_user:
# Overwrites the identity associated with the active PAM transaction handle!
session.target_user = submitted_user
pam_response = request.get_param("pam_response")
pam_status = session.pam_handle.respond(pam_response)
if pam_status == PAM_SUCCESS:
# Grants session tokens using the overwritten target_user rather than initial caller
auth_token = vsmserver.create_session(user=session.target_user)
return self.redirect_to_desktop(auth_token)

Because session.target_user was mutable and re-evaluated during the secondary conversation phase without verifying that pam_handle had actually completed an authentication chain for submitted_user, an attacker could supply low-privilege credentials or an account with a known OTP secret for step 1, and alter the username field to root during step 2. The PAM conversation concluded with PAM_SUCCESS, and vsmserver created the session under the privileges of root.

Cendio resolved the issue by cryptographically locking the session identity upon initial PAM handle creation, strictly prohibiting any alteration of target_user across conversational phases, and validating the PAM conversation context:

# Hardened session handling in patched ThinLinc releases
class WebLoginHandler:
def handle_multistep_response(self, request):
session_id = request.get_cookie("TL_SESSION_ID")
session = session_store.get(session_id)
# Enforce strict session validation and immutable user binding
if not session or not session.is_valid():
raise SecurityException("Invalid authentication transaction")
# Explicitly forbid any username parameter in subsequent conversation steps
if "username" in request.params:
session.terminate(reason="ILLEGAL_IDENTITY_MUTATION")
raise SecurityException("Identity redefinition during conversational PAM is prohibited")
pam_response = request.get_param("pam_response")
pam_status = session.pam_handle.respond(pam_response)
if pam_status == PAM_SUCCESS and session.pam_handle.get_user() == session.bound_user:
auth_token = vsmserver.create_session(user=session.bound_user)
return self.redirect_to_desktop(auth_token)

Exploitation of CVE-2026-119744 operates entirely over standard HTTPS requests directed at the ThinLinc Web Access port:

  1. Reconnaissance & Endpoint Discovery: The attacker probes public-facing IP ranges for ThinLinc Web Access instances running on TCP port 300 or 3001, identifying the /tlwebaccess/ endpoint and determining if multi-step authentication (e.g., OTP or login banner) is active.
  2. Initial Step Initiation: The attacker submits a valid credential pair for an unprivileged test account or an account configured for secondary validation. The server enters STATE_PAM_CONVERSATION and returns an HTML form requesting the secondary response.
  3. Session Identity Injection: In the second HTTP POST request carrying the OTP or banner response, the attacker inserts username=root into the request payload or HTTP headers.
  4. State Desynchronization & Verification: The tlwebaccess daemon processes the valid OTP or acknowledgment for the secondary challenge, marks the transaction as successful, and binds the newly spawned VNC/SSH session to root.
  5. Interactive VDI Desktop Takeover: The attacker receives an authenticated WebSocket token and connects to the ThinLinc display server, obtaining an interactive Linux X11/MATE/GNOME desktop or virtual terminal operating as root.

Detection requires inspecting web server access logs for anomalous parameter variations during multi-step authentication, along with auditing PAM session records and system authentication logs (auth.log / secure).

title: ThinLinc Web Access Multi-Step Authentication Bypass Attempt
id: 5a9b7c84-1e2f-48d6-9321-thinlincauth01
status: experimental
description: Detects suspicious identity mutation and parameter tampering during multi-step PAM authentication in Cendio ThinLinc tlwebaccess logs.
references:
- https://vulncheck.com/advisories/cendio-thinlinc-improper-authentication-via-web-access
- https://www.thinlinc.com/docs/security/bulletins/2026-11-06/
author: Hermes Codex Threat Intelligence
date: 2026-11-06
logsource:
category: webserver
product: thinlinc
detection:
selection_webaccess:
c-uri|contains: '/tlwebaccess/'
cs-method: 'POST'
selection_params:
cs-uri-query|contains:
- 'username=root'
- 'user=root'
selection_multistep:
cs-uri-stem|contains:
- 'step2'
- 'verify_otp'
- 'banner_ack'
condition: selection_webaccess and selection_params and selection_multistep
fields:
- c-ip
- cs-method
- cs-uri
- cs-user-agent
falsepositives:
- Legitimate administrative password reset workflows (rare for root via web)
level: critical
tags:
- attack.initial_access
- attack.t1078
- attack.t1133
Indicator TypeObservable / IndicatorAttribution & ContextFirst ObservedStatus
IPv4 Address193.142.146[.]211Weaponized ThinLinc auth bypass scanner2026-11-05ACTIVE
IPv4 Address185.220.101[.]78TOR exit node delivering forged tlwebaccess logins2026-11-06ACTIVE
IPv4 Address45.154.255[.]14Distributed reconnaissance node probing ports 300/30012026-11-05ACTIVE
Port / ProtocolTCP 300, TCP 3001ThinLinc Web Access daemon listening endpointsBaselineMONITOR
HTTP RequestPOST /tlwebaccess/loginForged multi-step payload with mismatched user2026-11-05MALICIOUS
Syslog Patterntlwebaccess.log: identity mismatchDesynchronized PAM conversation alert2026-11-05CONFIRMED

Administrators maintaining Cendio ThinLinc environments should implement immediate remediation actions:

The patch introduced by Cendio in tlwebaccess/login.py cryptographically binds the intermediate PAM handle to the authenticated identity through an HMAC-SHA256 signature generated during step 1. Any subsequent request attempting to finalize login under a modified username (user=root) triggers an immediate state-corruption abort (ERR_PAM_AUTH_STATE_CORRUPT).

Product BranchVulnerable VersionsFixed ReleasePatch Status
ThinLinc 4.21Pre-release4.21.0Official GA Release
ThinLinc 4.204.1.0 โ€“ 4.20.04.20.1Recommended Patch Release
ThinLinc 4.194.19.04.19.1Long-Term Support Backport
ThinLinc 4.184.18.04.18.1Long-Term Support Backport
ThinLinc 4.174.17.04.17.1Long-Term Support Backport
ThinLinc 4.164.16.04.16.1Long-Term Support Backport
ThinLinc 4.154.15.04.15.1Extended Security Maintenance

If an immediate upgrade cannot be scheduled during a maintenance window, administrators should temporarily stop and disable the web access service across all master and agent nodes:

Terminal window
# Stop and disable tlwebaccess immediately
sudo systemctl stop tlwebaccess.service
sudo systemctl disable tlwebaccess.service
# Verify the port (TCP 300/3001) is closed
sudo ss -tulpn | grep 300

Users can continue accessing remote desktop sessions through the native ThinLinc desktop client (which communicates directly over SSH on TCP port 22) without being exposed to the tlwebaccess logic flaw.