Skip to content
Reachability Analysis

CVE-2026-88779: Citrix NetScaler ADC and Gateway, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

CVE-2026-88779 is a memory overflow (CWE-119, improper restriction of operations within the bounds of a memory buffer) in NetScaler ADC and NetScaler Gateway. Citrix says it causes denial of service. The CVSS 4.0 score is 8.7: network attack, low complexity, no privileges, no user interaction, with high impact on availability only and none on confidentiality or integrity.

The flaw is reachable only when the appliance is set up as a SAML SP or a SAML IdP. An appliance with neither configured does not meet the vendor's precondition. The bulletin covers customer-managed appliances only; Citrix-managed cloud services and Citrix-managed Adaptive Authentication are updated by Cloud Software Group.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
The NetScaler build is before the fixed build for its trainOn the appliance CLI run show ns version and compare with the versions table. Check every node of an HA pair or cluster.
The appliance is configured as a SAML service provider (SP) or identity provider (IdP)Citrix says to inspect the configuration for entries matching add authentication samlAction (SAML SP) or add authentication samlIdPProfile (SAML IdP). Run show ns runningConfig | grep "add authentication samlAction" and show ns runningConfig | grep "add authentication samlIdPProfile". A hit on either command means the condition holds.
The SAML endpoint is reachable by the attacker, who Citrix and CISA describe as unauthenticated and remoteFind the virtual servers that use the SAML action or IdP profile, then check which of their addresses are published to the internet or untrusted networks. On the appliance CLI, list the SAML objects with show ns runningConfig | grep -E "samlAction|samlIdPProfile|samlPolicy|samlIdPPolicy", then find where they are attached with show ns runningConfig | grep -E "bind (authentication|vpn|aaa) vserver" and read each virtual server's address with show vserver <name> (or show authentication vserver <name>). A SAML virtual server whose address is reachable from the internet, or through a published URL, meets the condition. These are general NetScaler configuration commands; Citrix names only the two add authentication entries as the test.

Affected and fixed versions

Each fixed build and all later releases of the same train are fixed. The 13.1-FIPS and 13.1-NDcPP builds are a separate build stream from the standard 13.1 builds, which is why bulletin CTX697174 gives 13.1-37.282 for them and 13.1-64.28 for standard 13.1; compare a FIPS appliance only with its own row. Secure Private Access Hybrid deployments need their NetScaler instances moved to these builds too.
Product lineAffected buildsFirst fixed build
NetScaler ADC and Gateway 14.1Before 14.1-73.4114.1-73.41
NetScaler ADC and Gateway 13.1Before 13.1-64.2813.1-64.28
NetScaler ADC 14.1-FIPSBefore 14.1-73.41 FIPS14.1-73.41 FIPS
NetScaler ADC 13.1-FIPS and 13.1-NDcPPBefore 13.1-37.28213.1-37.282

If the fix cannot go in yet

  • No workaround is listed in bulletin CTX697174; the only change Citrix offers is an upgrade to the first fixed build for your train. The bulletin does not state downtime, so plan for the restart an ADC upgrade normally needs.
  • HA pair upgrade order (NetScaler documentation, page last published 12 Nov 2026): upgrade the secondary node first, run force failover so it becomes primary, then upgrade the original primary and fail over again if you want the original roles back. Both nodes must end on the same release. While the two nodes run different builds with different internal HA versions, HA configuration sync, command propagation, state sync and connection mirroring are disabled, so make changes and run the pair in that state only for the length of the upgrade.
  • Exposure-reducing step from the vendor's precondition: the flaw needs a SAML SP or IdP configuration. If neither is configured the appliance does not meet the precondition, but removing a SAML configuration stops SAML sign-in through that appliance, so it is a choice for you to weigh, not a vendor-recommended workaround.
  • CISA's KEV entry lists the required action: apply mitigations in accordance with vendor instructions, or discontinue use of the product if mitigations are unavailable.

What to look for

  • Citrix and CISA publish no log strings or indicator addresses for this flaw, and CISA marks forensic triage as not required. The impact is denial of service, so the trace an appliance leaves is a restart or crash. On the appliance shell, look for new crash dump directories under /var/core, restart and error lines around the event time in /var/log/ns.log, and a recent start time in the show ns stats output (System up since). These are general NetScaler places to look, not published indicators for this CVE.

The earliest dated mark of exploitation is CISA's, on 4 Oct 2026, 1 day after disclosure; exploitation may have begun earlier.

Exploitation reported so far

No report names the attacker or the first attack. Citrix's 3 Oct 2026 date is Pacific time and CISA publishes a date with no time, so the one-day gap is a calendar-date difference, not a measured interval.

Why static reachability settles it

Exposure depends on the build and on one configuration fact: whether the appliance acts as a SAML SP or IdP. Both are readable from the appliance with show ns version and a grep of the running configuration. KEV shows attacks happened, but only the configuration read tells you whether your appliance can be hit. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-88779: NVD record, read 19 Nov 2026
  2. CVE-2026-88779: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-88779: Citrix security bulletin CTX697174 (vendor advisory), read 19 Nov 2026
  4. CVE-2026-88779: NetScaler documentation, upgrade a high availability pair, read 19 Nov 2026

Last reviewed 19 Nov 2026.