Critical Citrix NetScaler RCE flaw CVE-2023-3519 allows web shell, malware deployment
Key Takeaways A critical remote code execution (RCE) vulnerability, CVE-2026-88771, affects Citrix NetScaler ADC and NetScaler Gateway products. The flaw, rated 9.5 on the CVSS scale, allows...
Key Takeaways
- A critical remote code execution (RCE) vulnerability, CVE-2026-88771, affects Citrix NetScaler ADC and NetScaler Gateway products.
- The flaw, rated 9.5 on the CVSS scale, allows unauthenticated attackers to execute arbitrary commands, deploy web shells, and deliver malware.
- Citrix has confirmed active exploitation of this vulnerability against unpatched systems.
- Patches are available, and immediate application is crucial, followed by comprehensive forensic investigation.
Critical Citrix NetScaler Flaw Exploited to Deploy Web Shells and Malware
A severe vulnerability impacting Citrix NetScaler ADC and NetScaler Gateway appliances is actively being leveraged by attackers to compromise systems, execute commands remotely, and install malicious payloads. This flaw, identified as CVE-2026-88771, presents a significant risk to organizations utilizing these products, particularly those with internet-facing deployments.
Table Of Content
The vulnerability stems from inadequate input validation, enabling unauthenticated attackers to achieve remote code execution. Citrix has assigned it a CVSS 4.0 score of 9.5, underscoring its critical severity. Importantly, exploitation does not rely on any optional features being enabled, broadening the attack surface. Citrix has officially confirmed that unpatched systems are currently under attack, as detailed in their security bulletin.
The consequences of a successful exploit extend beyond a momentary intrusion. Attackers are observed deploying web shells, which provide persistent remote access and control over the compromised appliance. Furthermore, the delivery of malware facilitates deeper system compromise and potential lateral movement within a network. Given that NetScaler devices often serve as critical network edge components, managing application access and user authentication, any compromise warrants an immediate and thorough investigation, even after security updates have been applied.
Exploitation Chain Details Emerge
Researchers from Zscaler’s ThreatLabz team identified a multi-stage exploitation process. Their analysis revealed a sophisticated attack chain involving log poisoning, subsequent command execution, and attempts to establish multiple web shells on affected systems.
During their observations, Zscaler also documented the deployment of a FreeBSD x64 malware payload. While the shared infrastructure for these attacks suggests potential coordination, Zscaler cautions that this could also simply indicate the reuse of common hosting or malware distribution services rather than a definitive link between threat actors.
Understanding the Attack Methodology
The observed attack sequence begins with attackers sending specially crafted requests to standard NetScaler web paths. These requests embed a unique marker and encoded commands within the User-Agent field, allowing attacker-controlled content to be written into the appliance’s access logs. Subsequently, malicious authentication requests are sent, designed to mimic a NetScaler process failure.
The strategic intent behind this method is to manipulate a vulnerable diagnostic process. When this process later handles the poisoned log entry, it inadvertently triggers and executes the appended commands. This delayed execution mechanism is critical, as the initial request merely sets the stage for the exploit, with the actual payload execution occurring at a later point when the log entry is processed.
Zscaler’s researchers documented attempts to create unauthorized files within appliance directories, modify web server configurations to enable PHP or Perl handling, and install scripts capable of executing further commands. These findings illustrate the adversary’s efforts to establish persistent access and control, though they represent attempted activities rather than confirmed successful compromise for every targeted system.
Further analysis by Zscaler revealed attempts to download and execute a Rust-based FreeBSD binary. The download command was observed naming the file kw2-freebsd-x64-s11 and placing it at /var/kw2s11. A rapid succession of similar activities, originating from at least 26 distinct IP addresses over a period of six to seven minutes, was noted. This indicates a concentrated effort to exploit the vulnerability, but the exact number of compromised systems remains unconfirmed.
This campaign follows a pattern of previous attacks leveraging NetScaler vulnerabilities. While other reports have detailed exploitation and web shell deployment on exposed NetScaler devices, it is important to note that different campaigns may involve different malware or threat actors.
Patching and Response
Citrix’s official guidance strongly recommends that affected customers apply the available security patches immediately. The initial recommended builds included NetScaler ADC and Gateway 14.1-73.37 and 13.1-64.23, or any subsequent releases within those branches. Zscaler’s advisory, updated on October 16, lists later builds, specifically 14.1-73.46 and 13.1-64.29, or newer versions. Administrators should always consult the latest Citrix security bulletin to ensure they are installing the most appropriate and currently supported update.
While patching is essential to prevent future exploitation, it does not guarantee that a system is free from compromise. Organizations must preserve all logs and forensic data. A thorough review of authentication and access logs is crucial for identifying suspicious markers, unusual shell syntax, unexpected file downloads, and abnormal requests. Additionally, checking for unfamiliar web files, altered HTTP server settings, unrecognized running processes, and suspicious outbound connections originating from the appliance is paramount. If a compromise is confirmed, Zscaler advises verifying configuration integrity and rotating all compromised credentials, tokens, and certificates.
Beyond the appliance itself, security teams should extend their investigation to connected systems. A compromised edge device can expose sensitive configuration information or provide a direct pathway into internal network segments. In the event of confirmed suspicious activity, the compromised device should be isolated, evidence preserved, potential exposure of accounts or secrets assessed, and the organization’s incident response plan activated. Applying the patch is a critical first step, but it must be followed by a comprehensive assessment to determine if an attacker has already gained unauthorized access.
Indicators of Compromise (IoCs)
| Type | Indicator |
|---|---|
| IPv4 | 45.153.212[.]101 |
| IPv4 | 46.233.40[.]20 |
| IPv4 | 46.236.167[.]143 |
| IPv4 | 46.33.33[.]95 |
| IPv4 | 49.150.197[.]119 |
| IPv4 | 78.190.152[.]64 |
| IPv4 | 81.10.79[.]197 |
| IPv4 | 82.167.14[.]7 |
| IPv4 | 95.105.74[.]172 |
| IPv4 | 100.38.125[.]66 |
| IPv4 | 102.213.132[.]123 |
| IPv4 | 102.222.146[.]45 |
| IPv4 | 103.181.212[.]245 |
| IPv4 | 103.197.249[.]161 |
| IPv4 | 103.83.146[.]100 |
| IPv4 | 111.92.128[.]89 |
| IPv4 | 114.145.49[.]215 |
| IPv4 | 120.244.160[.]182 |
| IPv4 | 125.62.88[.]26 |
| IPv4 | 130.12.182[.]7 |
| IPv4 | 154.183.158[.]198 |
| IPv4 | 154.241.254[.]9 |
| IPv4 | 174.60.63[.]37 |
| IPv4 | 177.52.203[.]23 |
| IPv4 | 183.63.88[.]227 |
| IPv4 | 190.117.56[.]56 |
| IPv4 | 195.62.37[.]119 |
| IPv4 | 207.48.184[.]10 |
Note: IP addresses are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.
What You Should Do
- Immediately Patch: Apply the latest security updates from Citrix for NetScaler ADC and NetScaler Gateway. Refer to the Citrix security bulletin for precise version requirements.
- Forensic Investigation: Even after patching, assume potential compromise. Conduct a thorough forensic analysis of all NetScaler appliances, especially those internet-facing.
- Log Review: Scrutinize access logs, authentication logs, and system logs for any suspicious entries, unexpected commands, unusual User-Agent strings, or signs of log poisoning.
- Check for Persistence: Look for unexpected web shells (e.g., .php, .pl, .sh files), unauthorized files in appliance directories, altered web server configurations, and unfamiliar running processes.
- Network Monitoring: Monitor outbound network connections from NetScaler devices for unusual activity or communication with unknown external IPs.
- Credential Rotation: If compromise is suspected or confirmed, immediately rotate all administrative credentials, API tokens, and certificates associated with the NetScaler appliances and any connected systems.
- Incident Response: Activate your organization’s incident response plan if signs of compromise are detected. Isolate affected systems, preserve evidence, and assess the scope of the breach.
- Review Connected Systems: Investigate systems connected to the NetScaler appliance, as a compromise of the edge device could provide a pivot point into the internal network.
Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.

![Top 9 Best Managed File Transfer (MFT) Solutions in 2026 [Ranked & Scored]](https://hackersradar.com/wp-content/uploads/2026/10/pexels_1792744374-150x150.jpg)

No Comment! Be the first one.