Attackers exploit critical Citrix NetScaler RCE to deploy web shells and malware

Critical Citrix NetScaler RCE Exploited to Install Web Shells and Malware

body { font-family: Arial, sans-serif; line-height: 1.6; color: #111; padding: 24px; max-width: 900px; margin: auto; }
h1, h2 { color: #111; }
table { border-collapse: collapse; width: 100%; margin: 16px 0; }
th, td { border: 1px solid #ddd; padding: 8px; text-align: left; vertical-align: top; }
th { background: #f7f7f7; }
figure { margin: 16px 0; text-align: center; }
figcaption { font-size: 0.9em; color: #555; }
code { background: #f0f0f0; padding: 2px 6px; border-radius: 4px; font-family: monospace; }
.center { text-align: center; }
.note { font-size: 0.95em; color: #333; margin-top: 8px; }
.callout { background: #eef6ff; border-left: 4px solid #6aa6ff; padding: 10px; margin: 16px 0; }

Critical Citrix NetScaler RCE Exploited to Install Web Shells and Malware

A critical remote code execution vulnerability in Citrix NetScaler ADC and NetScaler Gateway is being actively exploited to run commands on exposed appliances, install web shells and deploy malware.

Tracked as CVE-2026-88771, the flaw permits an unauthenticated attacker to execute commands remotely. Citrix disclosed the vulnerability on September 27, 2026, and confirmed that some unpatched appliances were being exploited.

According to a Zscaler ThreatLabz analysis, the vulnerability carries a CVSS score of 9.8 under v3.1 and 9.5 under v4.0. The activity is particularly dangerous because NetScaler devices commonly sit at the edge of networks and provide remote access and application traffic handling, making them valuable targets.

A web shell can provide persistent access to a compromised appliance, and a separate malware implant can give attackers an additional foothold. The campaign also demonstrates that patching alone may not be sufficient: organizations must verify whether attackers already modified files, settings or logs.

Zscaler ThreatLabz researchers identified a staged exploitation chain that used log poisoning, command execution, attempts to place web shells and delivery of a FreeBSD malware implant.

How the exploitation chain worked

In the observed attacks, initial requests to common NetScaler web paths included a distinctive INDEX: marker and encoded content in the User-Agent header. Those requests were intended to get attacker-controlled data written into web access logs; the initial requests did not themselves execute the full payload.

Attackers then sent crafted authentication requests that mimicked a Packet Processing Engine (PPE) failure message. A vulnerable diagnostic process — a Perl script used for diagnostics — later processed matching log entries and failed to safely handle attacker-controlled characters in the forged message.

When that script processed the poisoned log entry, appended commands could execute with the script’s privileges. This delayed, multi-step approach explains why seemingly ordinary web or login traffic can be part of a larger attempt to compromise an appliance.

Attack chain (Source – Zscaler)

The payloads observed attempted to create web-accessible files, enable PHP or Perl handling on the web server, and place files named Nx_7508.php and Nx_7508.pl. Researchers also observed attempts to download and run a 64-bit FreeBSD binary named kw2-freebsd-x64-s11.

Zscaler reported that the infrastructure used to serve the FreeBSD binary had previously appeared in activity targeting Magento and Adobe Commerce via CVE-2026-75650 (style-smuggling activity referenced as StyleSmuggler). That overlap is an investigative lead but not definitive proof that the same actor conducted both campaigns.

Previous reporting has documented other incidents where attackers used NetScaler vulnerabilities to deploy web shells. Those earlier incidents provide context but relate to different flaws and should not be treated as evidence that the same operators are responsible for this exploitation chain.

What organizations should do

Citrix published fixed builds. According to the Zscaler report, the affected builds and minimum patched versions include:

  • NetScaler ADC and Gateway: 14.1-73.46 or later, and 13.1-64.29 or later.
  • 14.1-FIPS: 14.1-73.46 FIPS or later.
  • 13.1-FIPS and 13.1-NDcPP: 13.1.37.283 or later.

Administrators should verify the exact build running on their appliances and upgrade promptly. Before updating, preserve relevant evidence where possible, including remote syslog data, technical support bundles and any available core dumps.

After or while preparing to update, review authentication and web access logs for suspicious INDEX: User-Agent values; forged “pitboss PPE” failure messages; unexpected requests to the HTTP and authentication paths listed in the indicators section below; and appliance-initiated connections to unfamiliar hosts. Also inspect for unapproved web files, changed web-server settings and suspicious processes.

If compromise is suspected, isolate the appliance while preserving evidence and rotate credentials, tokens and certificates that the appliance could access. Patching prevents further exploitation of the vulnerability but does not remove an existing web shell or implanted malware — remediation teams must search for and remove any malicious files or processes found.

Responders should use the indicators provided below for this incident and consult the relevant vendor guidance for any other NetScaler flaws when comparing current activity to earlier disclosures.

Indicators of compromise (IoCs)

Type Indicator Context
Source IP 45.153.212[.]101 Reported source address
Source IP 46.233.40[.]20 Reported source address
Source IP 46.236.167[.]143 Reported source address
Source IP 46.33.33[.]95 Reported source address
Source IP 49.150.197[.]119 Reported source address
Source IP 78.190.152[.]64 Reported source address
Source IP 81.10.79[.]197 Reported source address
Source IP 82.167.14[.]7 Reported source address
Source IP 95.105.74[.]172 Reported source address
Source IP 100.38.125[.]66 Reported source address
Source IP 102.213.132[.]123 Reported source address
Source IP 102.222.146[.]45 Reported source address
Source IP 103.181.212[.]245 Reported source address
Source IP 103.197.249[.]161 Reported source address
Source IP 103.83.146[.]100 Reported source address
Source IP 111.92.128[.]89 Reported source address
Source IP 114.145.49[.]215 Reported source address
Source IP 120.244.160[.]182 Reported source address
Source IP 125.62.88[.]26 Reported source address
Source IP 130.12.182[.]7 Reported source address
Source IP 154.183.158[.]198 Reported source address
Source IP 154.241.254[.]9 Reported source address
Source IP 174.60.63[.]37 Reported source address
Source IP 177.52.203[.]23 Reported source address
Source IP 183.63.88[.]227 Reported source address
Source IP 190.117.56[.]56 Reported source address
Source IP 195.62.37[.]119 Reported source address
Source IP 207.48.184[.]10 Reported source address
Download server 209.141.43[.]95 Server linked to the FreeBSD payload download
Downloaded file kw2-freebsd-x64-s11 FreeBSD x64 implant filename
File path /var/kw2s11 Reported malware destination path
Web shell / file names Nx_7508.php, Nx_7508.pl Names used in observed deployment attempts
Fingerprint file Nx_7508.html Name used in observed appliance fingerprinting
User-Agent marker INDEX: Marker associated with staged content in access logs
Authentication log marker pitboss PPE Forged failure text observed in crafted requests
HTTP path /logon/LogonPoint/tmindex.html Observed request path
HTTP path /logon/LogonPoint/index.html Observed request path
HTTP path /vpn/index.html Observed request path
HTTP path /logon/tmindex.html Observed request path
Authentication path /nf/auth/doAuthentication.do Observed request path
Authentication path /cgi/login Observed request path

Note: IP addresses and domains are intentionally defanged (for example, [.]) to prevent accidental resolution or linking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal or your SIEM.

Update defenses against new malware as soon as it appears. Integrate threat intelligence feeds with data from SOC operations.
spot_img

More from this stream

Recomended