Skip to content
RESEARCH INDEX BREACHROAD / INTELLIGENCE NOTE

NetScaler CVE-2026-19490: critical authentication bypass with no workaround

Citrix fixed an authentication bypass and memory overflow in NetScaler ADC and Gateway. We explain SAML, SIP ALG, affected builds and HA rollout.

PUBLIC RESEARCH
AUTHOR
/ CEO Breachroad · OSCP · PNPT
PUBLISHED
19 August 2026
READING TIME
16 min read
TOPIC
Vulnerabilities and CVEs
NetScaler CVE-2026-19490: critical authentication bypass with no workaround

Citrix published a critical advisory for NetScaler ADC and NetScaler Gateway on 19 August 2026. CVE-2026-19490 is an authentication bypass through an alternate path with a CVSS 4.0 score of 9.3. CVE-2026-19489 is a memory flaw that can cause unpredictable behaviour or denial of service, scoring 8.8. The vendor provides no workaround and recommends urgent upgrading.

The official advisory does not state that either issue is actively exploited. It would therefore be wrong to invent a campaign or call it another “CitrixBleed.” Priority remains high because NetScaler commonly sits at the network edge handling VPN, ICA Proxy, AAA and SAML. Authentication bypass on this device affects the trust boundary in front of internal applications.

Affected and fixed releases

Citrix lists these supported ranges and fixed builds:

  • NetScaler ADC and Gateway 14.1 before 14.1-73.32 — update to 14.1-73.32 or later;
  • NetScaler ADC and Gateway 13.1 before 13.1-63.21 — update to 13.1-63.21 or later;
  • NetScaler ADC 14.1 FIPS before 14.1-73.32 FIPS — update to that build or later;
  • NetScaler ADC 13.1 FIPS and NDcPP before 13.1-37.277 — update to 13.1-37.277 or later.

Secure Private Access Hybrid deployments using NetScaler instances are also affected and require appliance upgrades. The bulletin applies to customer-managed NetScaler ADC and Gateway. Citrix-managed cloud services and Citrix-managed Adaptive Authentication are updated by the provider.

This responsibility split belongs in the risk record. “We use Citrix” does not establish ownership. Determine whether the customer manages the NetScaler image, consumes a fully managed service or, in a hybrid model, owns each relevant instance.

CVE-2026-19490: alternate-path authentication bypass

The vulnerability is described as authentication bypass using an alternate path. The appliance must be configured as a Gateway — SSL VPN, ICA Proxy, CVPN or RDP Proxy — or an AAA virtual server. Additional prerequisites differ by release family and earlier build.

For 14.1-43.56 and later, the vulnerable path also requires a configured SAML action plus a Gateway or AAA vserver. The same rule applies to 14.1-66.68 FIPS and later. For 14.1-43.55 and earlier, Gateway or AAA configuration is sufficient. On 13.1-61.28 and later, a SAML action is required; 13.1-61.27 and earlier are in scope with Gateway or AAA. For 13.1 FIPS, the prerequisite is Gateway or AAA vserver configuration.

These prerequisites are not vendor workarounds. They help identify whether an instance has a reachable vulnerable path. Citrix still lists no workaround. An organisation should not hastily remove SAML or redesign a production VPN without testing when a supported fixed build is available.

An alternate-path bypass can allow a request to reach a privileged path without completing normal identity checks. Effective access depends on vserver configuration, session policies, resources behind the Gateway and application controls. It is unsafe to assume every backend reauthenticates a user — central AAA exists precisely to provide that boundary.

Checking CVE-2026-19490 prerequisites

Citrix provides configuration patterns for locating SAML actions, authentication vservers and VPN vservers. Teams can search an exported show ns config and retain the result as evidence. Vendor patterns include lines beginning add authentication samlAction, add authentication vserver and add vpn vserver.

A positive result does not prove exploitation. It proves part of the prerequisite and raises priority. A negative result also needs care: configuration may be generated, split across partitions, held in an ADM template or differ between HA nodes. Inspect active and passive appliances, saved configuration and running state.

Do not attempt to bypass authentication on production. Defensive validation uses version, configuration and post-update regression testing. An authorised isolated lab with synthetic accounts can confirm correct flow enforcement without developing an exploit.

CVE-2026-19489: SIP ALG memory overflow

CVE-2026-19489 is an out-of-bounds memory operation causing unpredictable behaviour or denial of service. The prerequisite is SIP ALG enabled for a Large Scale NAT group. Citrix suggests locating the pattern add lsn group.*sipalg.*.

SIP ALG parses and modifies SIP protocol information so voice sessions operate through address translation. Its parser handles network-controlled data and session state, so a memory defect can affect appliance stability. The bulletin does not support expanding the stated impact into confirmed RCE. It identifies unpredictable behaviour or DoS.

NetScaler availability is often essential for sign-in, VPN and application publishing. Even DoS can disconnect staff, call-centre operations or administrative access during another incident. In HA, determine whether malicious traffic or synchronised state can affect both nodes and whether failover merely transfers traffic to an equally vulnerable release.

HA cluster rollout

Start with inventory: management address, vservers, build, FIPS or NDcPP edition, active/passive role, ADM, last backup and business owner. Save configuration and validate the target release against licensing, platform, extensions, EPA, nFactor, SAML, GSLB and application monitors.

A typical HA change preserves service by updating the passive node, testing synchronisation and monitors, performing controlled failover, observing traffic, updating the second node and returning to the target topology. The exact procedure must follow Citrix documentation and the deployed architecture. Do not improvise sequence on a critical Gateway.

After deployment:

  • confirm the build on both nodes and in ADM;
  • verify configuration is saved and synchronised;
  • test SAML, nFactor, VPN, ICA Proxy, CVPN, RDP Proxy and AAA;
  • check service monitors and session state after failover;
  • update DR images, templates and rebuild procedures;
  • scan the version from the management network and retain evidence;
  • remove firmware and backups from any public location.

Where an instance is no longer supported, remaining on the old build while assuming the CVE is absent is not a remedy. Plan migration to a supported branch or retire the appliance.

Hunting and post-compromise actions

Absence of active-exploitation reporting does not eliminate the value of review for high-exposure instances. Examine unusual authentication successes and failures, sessions without the expected SAML sequence, Gateway and AAA anomalies, configuration changes, new files, crashes and restarts. Correlate NetScaler, identity-provider, VPN, backend application and endpoint logs.

If evidence suggests bypass, upgrading contains the vulnerability but does not remove effects. Consider invalidating sessions, tokens and cookies, changing administrative credentials, preserving configuration and memory evidence under procedure, and reviewing access to resources behind the Gateway. Do not clean the appliance before collecting evidence.

Session invalidation and correlation are Breachroad conclusions, not steps in the vendor bulletin. Scope should follow evidence and authentication architecture.

Vendor facts and Breachroad analysis

Affected releases, fixed builds, prerequisites, CVSS and absence of a workaround come from CTX696939. The official page does not confirm active exploitation. HA ordering, hunting, rotation and passive-node checks are Breachroad analysis.

Gateway response is a good joint exercise for network, IAM, SOC and application owners. Cybersecurity training for technical teams develops shared decisions and communication, while an IT security audit can verify builds, management segmentation, SAML, HA and rollout evidence.

Sources

SHARE / COPY