Skip to content
Reachability Analysis

CVE-2026-19490: 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-19490 is an authentication bypass using an alternate path or channel (CWE-288) in NetScaler ADC and NetScaler Gateway. An unauthenticated attacker who can reach a Gateway or AAA virtual server over the network may bypass authentication. Citrix rates it 9.3 on CVSS 4.0 (network, low complexity, no privileges, no user interaction, high impact on confidentiality, integrity and availability of the appliance).

Whether a given appliance is exposed depends on its build and its configuration. The flaw applies only to appliances set up as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or as an AAA virtual server. On newer builds Citrix narrows this further to appliances that also use a SAML action. Citrix says the bulletin covers customer-managed appliances only: Citrix-managed cloud services and Citrix-managed Adaptive Authentication are updated by Cloud Software Group.

The same bulletin, CTX696939, also covers CVE-2026-19489, a separate memory overflow that needs SIP ALG enabled on a Large Scale NAT group. The two share the same fixed builds.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the NetScaler ADC or Gateway build is before 14.1-73.32, 13.1-63.21, 14.1-73.32 FIPS or 13.1-37.277On the appliance CLI run show ns version and compare the build with the versions table (14.1 before 14.1-73.32, 13.1 before 13.1-63.21, 14.1 FIPS before 14.1-73.32 FIPS, 13.1 FIPS and NDcPP before 13.1-37.277). Check every node of an HA pair or cluster.
it is configured as a Gateway or AAA virtual server, and also has a SAML action on newer buildsCitrix says to inspect the configuration for these strings. Gateway virtual server (SSL VPN, ICA Proxy, CVPN or RDP Proxy): show ns runningConfig | grep "add vpn vserver". AAA virtual server: show ns runningConfig | grep "add authentication vserver". SAML action: show ns runningConfig | grep "add authentication samlAction". Any hit on the first two means a Gateway or AAA virtual server is present. Which builds also need the SAML hit: on 14.1-43.56 or later, 14.1-66.68-FIPS or later and 13.1-61.28 or later (non-FIPS), Citrix lists the flaw as applicable only with a SAML action, so no samlAction hit means those builds are not exposed. On 14.1-43.55 or earlier, 13.1-61.27 or earlier and 13.1-FIPS builds, a Gateway or AAA virtual server alone is enough. The bulletin states the 13.1-FIPS rule without a SAML requirement. It lists no rule for 13.1-NDcPP, so assume a Gateway or AAA virtual server alone is enough on that build.
the virtual server is reachable by the attacker, who needs no credentialsList the virtual server addresses and ports with show vpn vserver and show authentication vserver, then check which are published to the internet or to untrusted networks in your firewall rules.

Affected and fixed versions

Each fixed build and all later releases of the same train are fixed. NVD words the range as 'through 73.32' and 'through 63.21', but the Citrix bulletin says 'before' those builds and names them as the fixes. 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.3214.1-73.32
NetScaler ADC and Gateway 13.1Before 13.1-63.2113.1-63.21
NetScaler ADC 14.1-FIPSBefore 14.1-73.32 FIPS14.1-73.32 FIPS
NetScaler ADC 13.1-FIPS and 13.1-NDcPPBefore 13.1-37.27713.1-37.277

If the fix cannot go in yet

  • No workaround: Citrix lists 'None' under workarounds and mitigating factors. The fix is the first fixed build for your train (see the versions table). Plan for the restart an ADC upgrade normally needs: the bulletin states no downtime, no upgrade order for HA pairs or clusters and no step to end existing sessions.
  • Not from Citrix: until the upgrade is in, restrict which source addresses can reach the Gateway and AAA virtual servers, for example with firewall rules or ACLs that allow only known partner or office ranges. Cost: remote users outside those ranges lose VPN or ICA access, so this suits appliances with a known user population and not a public VPN. It narrows exposure and does not remove the flaw, because the vendor lists no workaround.
  • CISA's KEV entry requires applying the vendor's mitigations in line with BOD 26-04 and its forensics triage requirements, or discontinuing use of the product if mitigations are unavailable. The KEV entry marks forensic triage as Yes for this CVE.

What to look for

  • Citrix and CISA publish no log strings, session artifacts or indicator addresses for this CVE. The bypass skips authentication, so a successful attack leaves no failed-login trail to search for. Treat an unpatched Gateway or AAA appliance that was reachable from 19 Aug 2026 as a candidate for triage.
  • Collect this evidence from each appliance before you upgrade, because the upgrade restarts it: /var/log/ns.log and the rotated ns.log.* files for Gateway logins (the SSLVPN LOGIN lines, which carry SessionId, User and Client_ip) and AAA virtual server login lines that have no matching authentication event from the identity provider (Citrix names no log message for this CVE, so these are NetScaler's general session records); the list of live AAA and Gateway sessions with show aaa session and the matching connection lists, compared with your user directory; and the performance-counter data that nsconmsg reads, saved with a configuration backup and a copy of show ns runningConfig.
  • Follow CISA's forensic triage steps for the rest: the KEV entry requires them under BOD 26-04, with target times that run from the KEV addition on 9 Sep 2026.

The earliest dated mark of exploitation is CISA's, on 9 Sep 2026, 21 days after disclosure; exploitation may have begun earlier.

Exploitation reported so far

The KEV entry describes the flaw as an authentication bypass on appliances configured as an AAA virtual server or as a Gateway, and lists ransomware campaign use as Unknown. No report names the date of first attack or the attacker.

Why static reachability settles it

Exposure depends on the build and on whether the appliance runs a Gateway or AAA virtual server, plus a SAML action on newer builds. All of that is readable from the appliance with show ns version and a grep of the running configuration, so a configuration read settles it faster than a CVSS score or a feed. KEV confirms exploitation, which makes the check urgent but does not say whether your appliance is exposed. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-19490: NVD record, read 19 Nov 2026
  2. CVE-2026-19490: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-19490: Citrix security bulletin CTX696939 (vendor advisory), read 19 Nov 2026
  4. CVE-2026-19490: CISA BOD 26-04 implementation guidance (forensic triage steps), read 19 Nov 2026

Last reviewed 19 Nov 2026.