ZERO-DAY

Two Unpatched Citrix NetScaler RCE Zero-Days Exploited in the Wild

No Patch, No IoCs, No Bulletin. watchTowr says two unpatched remote code execution flaws in Citrix NetScaler ADC and Gateway were exploited before any fix existed.

Matt Lucas  |  September 27, 2026  |  5 min
Editorial hero illustration
2
Unpatched NetScaler RCE zero-days
0
Vendor patches, workarounds or IoCs published
Sep 15
NetScaler 13.1 reached End of Maintenance
Sep 28
Week Citrix fixes are expected
TL;DR
  • What: watchTowr reported on September 26 that two unpatched remote code execution flaws in Citrix NetScaler ADC and NetScaler Gateway are being exploited in the wild, found during forensic investigations.
  • Impact: NetScaler sits at the network edge handling VPN, remote access and authentication, so code execution there exposes stored secrets, certificates, user sessions and a pivot point into the internal network.
  • Fix / mitigation: No patch, workaround or IoC exists yet; Citrix fixes are expected early in the week of September 28, and until then operators must choose between isolating, powering off or accepting the risk, and should treat exposed appliances as possibly compromised.
  • Who's at risk: Every organization running internet-facing NetScaler ADC or Gateway, including those already on the August 19 builds 14.1-73.32 and 13.1-63.21, since Citrix has not said which versions are affected.

Two remote code execution vulnerabilities in Citrix NetScaler ADC and NetScaler Gateway are being exploited in the wild with no patch available, according to security firm watchTowr. Citrix had not confirmed the flaws, issued a bulletin, or published a fix as of Sunday, September 27. There is no vendor workaround and no published indicators of compromise. Some administrators have already taken their appliances offline rather than wait.

NetScaler appliances terminate VPN sessions, broker remote access, balance load and authenticate users. Code execution on that box gives an attacker the credentials, session tokens, certificates and private keys that flow through it, plus a foothold inside the perimeter.

What watchTowr Said, and What It Did Not

watchTowr first posted on X on September 26 that it was responding to rumors of several unpatched NetScaler RCE vulnerabilities in the wild, adding: "While details are scarce, the information is credible." A follow-up at 22:19 UTC gave the fuller account: two vulnerabilities, both remote code execution, both unpatched, both exploited before any fix existed, both discovered during forensic investigations. It said Citrix communications and patches are expected early in the week of September 28 and directed further questions to Citrix.

watchTowr has published no technical evidence, named no victim and not said whose forensic investigations found the exploitation. The firm has a track record on this product: in August it showed that a NetScaler heap overflow Citrix patched in June could be turned into remote code execution.

These are new flaws. They are separate from the authentication bypass CVE-2026-19490, which Citrix fixed on August 19 and CISA added to the Known Exploited Vulnerabilities catalog on September 9. Being on the August builds (14.1-73.32 or 13.1-63.21) or newer does not mean you are safe: Citrix has not said whether those builds are affected.

Admins Are Pulling the Plug

Reports of shutdown advice appeared on Reddit the same day. An administrator on r/Citrix wrote that their IT supplier's security team phoned to advise shutting down their NetScalers immediately, without giving details. Others in the thread said their organizations had done the same. Where the suppliers' warning originated has not been established.

With no bulletin, the decision for every NetScaler owner right now comes down to three options: keep it online and accept the risk, isolate it, or power it off. The second decision is whether to treat it as already compromised. For any internet-facing appliance, the answer to that second question should be yes until you have evidence otherwise.

Patching Will Not Tell You If You Were Hit

Because exploitation happened before any fix existed, installing the patch closes the door but says nothing about who already walked through it. The precedent is recent. In 2025, after a NetScaler flaw was exploited as a zero-day against Dutch organizations, the Netherlands' National Cyber Security Center (NCSC-NL) warned that updating alone did not remove the risk, because attackers could retain access gained before the patch, and told administrators to run its check scripts.

Plan the patch window and the investigation as two separate jobs. Capture evidence before you patch, reboot or reimage, because each of those can destroy the artifacts you need.

Citrix's Existing Compromise Guidance

Citrix already publishes a playbook for a suspected NetScaler compromise. It applies here:

The NCSC-NL 2025 check scripts cover a live appliance, core dumps and full NetScaler images. They have limits. The live-appliance README says the script looks for files that indicate compromise, is not specific to any one vulnerability, and carries no guarantee of effectiveness. The code was last updated in September 2025, so it will not know about artifacts unique to these new flaws. A clean result is a data point, not a clearance.

The 13.1 Problem

NetScaler 13.1 reached End of Maintenance on September 15, twelve days before this disclosure. Citrix has not said whether 13.1 will receive a fix. If you still run 13.1, start planning the move to 14.1 now: you may be forced to upgrade major versions under active exploitation, with no guarantee a 13.1 build is coming.

RedEye Assessment

The sourcing is thin: one vendor, no evidence, no victims, no CVE. It is also consistent with the last three years of NetScaler history, where edge appliance zero-days became mass exploitation within days of disclosure. Treat the absence of a bulletin as a reason to act early, not a reason to wait.

What to Do Before Monday

Fix It Yourself

Everything above is what happened. This is what to run. The check commands change nothing.

Check whether you are exposed

Show the exact NetScaler build (compare against the Citrix bulletin when it ships); set NS_HOST to your NSIP first

ssh nsroot@"$NS_HOST" 'show ns version'

List files changed in the last 30 days under web-served and VPN directories, a common webshell drop location in past NetScaler intrusions (read-only)

ssh nsroot@"$NS_HOST" 'shell find /netscaler/ns_gui /var/vpn /var/netscaler/logon -type f -mtime -30 -ls'

From an external host, test whether the management HTTPS interface answers on the internet (prints an HTTP status code only)

curl -sk -o /dev/null -m 10 -w '%{http_code}\n' "https://$NS_PUBLIC_IP/"

Close it

NO PATCH EXISTS YET. Step 1, preserve evidence: generate a Citrix tech support bundle on the appliance before any change

ssh nsroot@"$NS_HOST" 'show techsupport'

Step 2, copy the bundle off the appliance for forensics (path printed by the previous command lands under /var/tmp/support)

scp -r nsroot@"$NS_HOST":/var/tmp/support ./netscaler-evidence-$(date +%Y%m%d)

Step 3, containment if you choose to take the appliance offline: power it off only after evidence is copied and your VPN users have an alternate path

ssh nsroot@"$NS_HOST" 'shell shutdown -p now'

Prompts for the agent you already run

Before Citrix ships a fix, to scope exposure across your fleet

You are helping me scope exposure to two unpatched Citrix NetScaler RCE zero-days. Using the host list in netscaler_hosts.txt (one NSIP per line), SSH to each as nsroot and run only read-only commands: 'show ns version', 'show ns ip', and 'shell find /netscaler/ns_gui /var/vpn /var/netscaler/logon -type f -mtime -30 -ls'. Build a table of host, build number, whether management access is enabled on any IP that is also a public VIP or SNIP, and any recently modified files. Flag any 13.1 builds as End of Maintenance. Show every command you run and its raw output. Do not change configuration, do not reboot, do not delete or move any file. Stop and ask me before any action that is not read-only.

After you decide to treat an appliance as compromised

You are helping me respond to a suspected compromise of Citrix NetScaler host $NS_HOST. Step 1: run 'show techsupport' and copy the resulting bundle from /var/tmp/support to ./evidence/ on this machine, then compute SHA-256 hashes of every copied file. Step 2: run 'show ns runningConfig' and extract every service account, LDAP or RADIUS bind account, and every certkey name into a rotation checklist in rotation.md. Show your work and every command. Do not rotate credentials, revoke certificates, disable interfaces or shut down the appliance yourself: stop after producing the evidence hashes and rotation.md and wait for my approval.

What to alert on

Forward NetScaler /var/log/ns.log and /var/log/httpaccess.log to your SIEM via remote syslog and alert on two things until IoCs are published. First, process execution where the parent is the appliance web server (httpd running as user nobody) and the child is sh, bash, csh, python, perl, curl or nc: NetScaler has no legitimate reason for its web tier to spawn shells. Second, any file creation or modification under /netscaler/ns_gui, /var/vpn or /var/netscaler/logon outside a change window, especially .php, .xhtml or .js files. Correlate with SHELL or CMD_EXECUTED entries in ns.log from sessions that did not originate on your management network.

Questions about your exposure?

RedEye Security provides assessments for organizations that need to understand their real risk.

Talk to us