Someone found the staff entrance to the castle and it doesn't need a key
CVE-2026-19490 is an authentication bypass via alternate path (CWE-288) in Citrix NetScaler ADC and NetScaler Gateway. It affects all deployments configured as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server — which is the *canonical* deployment mode for these appliances. Affected version ranges are 14.1 before 14.1-73.32 and 13.1 before 13.1-63.21, plus corresponding FIPS (14.1-73.32 FIPS) and NDcPP (13.1-37.277) builds. The CVSS 4.0 vendor score is 9.3 Critical with vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L. No authentication is required, no user interaction is needed, and complexity is low.
The vendor severity of 9.3 Critical is, if anything, *understated* for the operational reality. NetScaler Gateway exists to be the internet-facing authentication gate for remote users — every single Gateway deployment is reachable from the internet by design. An authentication bypass on this component is functionally equivalent to removing the front door of the corporate network. Citrix lists no workarounds, meaning patching is the only option. With ~40,000 NetScaler instances visible on Censys as of March 2026, the exposed population is large and the attacker economics are extremely favorable. This is the same class of perimeter auth-bypass that drove mass exploitation in CitrixBleed (CVE-2023-4966) and CVE-2026-3055.
4 steps from start to impact.
Identify exposed NetScaler Gateway
http.title:"NetScaler" or TLS certificate fingerprinting). Censys reports ~40,000 exposed instances as of early 2026. The login page itself confirms the appliance role (Gateway/AAA vserver) and often leaks the firmware version in HTTP headers or JavaScript bundles.- Target runs NetScaler ADC or Gateway in Gateway or AAA vserver mode
- Appliance is internet-facing (inherent to Gateway role)
- None — Gateway appliances are internet-facing by design
Exploit alternate authentication path
- Vulnerable firmware version (14.1 < 14.1-73.32 or 13.1 < 13.1-63.21)
- Gateway or AAA vserver configuration active
- Patched versions close the alternate path entirely
- No public PoC as of disclosure day (2026-08-19) — but this class of bug is trivially reproducible once the patch diff is available
Gain authenticated session as arbitrary user
- Step 2 succeeds
- Network microsegmentation behind the Gateway may limit lateral movement
- MFA on downstream resources (not the Gateway itself) may slow pivoting
Lateral movement into internal network
ns.conf), SAML signing keys, and session tokens for all active users. These credentials enable direct domain compromise without additional exploit chains.- Internal network reachable from Gateway VPN tunnel
- Credentials or keys stored on appliance
- EDR on internal endpoints may detect post-exploitation
- Network segmentation between VPN VLAN and sensitive tiers
The supporting signals.
| In-the-Wild Exploitation | Not yet confirmed. Disclosed today (2026-08-19). No KEV listing. Given the Citrix perimeter attack surface history (CitrixBleed, CVE-2026-3055, CVE-2026-8452), weaponization is expected within days to weeks. |
|---|---|
| Proof-of-Concept | No public PoC as of 2026-08-19. However, CWE-288 auth bypasses are typically trivially reproducible from patch diffs. Expect weaponized PoC within 48–72 hours of patch availability, based on historical Citrix vuln timelines. |
| EPSS Score | Not yet scored (day-zero disclosure). Historical Citrix Gateway auth-bypass CVEs have scored in the 95th+ percentile within weeks. |
| KEV Status | Not listed as of 2026-08-19. High probability of future listing given product class and severity. |
| CVSS Vector | CVSS 4.0: 9.3 — AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L. Network-accessible, no auth, no interaction, no complexity. Full CIA impact on the vulnerable system. No CVSS 3.x score from NVD yet. |
| Affected Versions | NetScaler ADC & Gateway 14.1 < 14.1-73.32, 13.1 < 13.1-63.21; NetScaler ADC FIPS 14.1 < 14.1-73.32 FIPS; NetScaler ADC FIPS/NDcPP 13.1 < 13.1-37.277 |
| Fixed Versions | 14.1-73.32, 13.1-63.21, 14.1-73.32 FIPS, 13.1-37.277 FIPS/NDcPP |
| Exposure Data | Censys reported ~40,000 exposed NetScaler instances (March 2026). Shodan shows 56,000+ NetScaler services. The vast majority of Gateway deployments are internet-facing by design. |
| Disclosure Date | 2026-08-19 (today). Bulletin: CTX696939 |
| Vendor Workarounds | None. Citrix explicitly states no mitigations or workarounds exist. Patching is the sole remediation. |
noisgate verdict.
The single most decisive factor is role identity — NetScaler Gateway is a canonically internet-facing perimeter authentication appliance, and this is an unauthenticated authentication bypass on it. The combination of zero-prerequisite remote exploitation (AV:N/AC:L/PR:N/UI:N) on a component whose entire purpose is to be the internet-reachable front door, with ~40,000 exposed instances and no vendor workaround, places this squarely at CRITICAL with no friction-based grounds for downgrade.
Why this verdict
- No authentication required: The CVSS vector explicitly confirms PR:N. This is a zero-credential attack against a login page — the most favorable attacker economics possible.
- Role multiplier: NetScaler Gateway is a *canonical* network edge appliance. By definition, ≥95% of Gateway deployments are internet-facing — that is the product's entire purpose. An auth bypass on the perimeter VPN gateway gives an attacker a beachhead equivalent to a valid employee VPN session. The blast radius extends from the appliance (credential extraction, TLS key theft) through the entire internal network (VPN tunnel routing). This is fleet-scale impact. The verdict floor is CRITICAL per the network edge appliance rule.
- No workaround exists: Citrix explicitly states no mitigations are available. This eliminates the usual friction point of 'deploy WAF rule while you plan patching.' The only path is firmware upgrade.
- Historical exploitation pattern: Every major Citrix Gateway auth-adjacent vulnerability in the past 3 years (CVE-2023-4966 CitrixBleed, CVE-2023-3519, CVE-2026-3055, CVE-2026-8452) has been weaponized rapidly, often within days. Ransomware operators (LockBit, ALPHV successors) have specifically targeted NetScaler as an initial access vector.
- Massive exposed population: ~40,000–56,000 instances visible on internet scanning platforms. This is not a niche product with a handful of deployments — it is a primary enterprise remote access platform.
Why not higher?
A 9.6 is already near the ceiling. The only gap to 10.0 is the absence of *confirmed* in-the-wild exploitation and a public PoC as of disclosure day. Once either appears, the operational urgency increases but the technical severity assessment would not meaningfully change.
Why not lower?
Every friction audit point *favors* the attacker: the target is internet-facing by design (no network position required), no credentials needed, no user interaction, low complexity, no workaround available, and the product class has a proven track record of rapid mass exploitation. There is no legitimate basis to assess below CRITICAL. The blast radius — perimeter gateway to internal network — is the most consequential initial-access scenario in enterprise security.
What to do — in priority order.
- Restrict management and Gateway VIPs to known IP ranges via ACLs — If your Gateway serves a defined user population (e.g., corporate IP ranges, specific countries), apply network ACLs on the NetScaler or upstream firewall to drop traffic from unexpected sources. This reduces the exposed attack surface while you patch. Deploy within the 3-day noisgate mitigation SLA for CRITICAL findings.
- Enable and monitor NetScaler audit logging for sessionless authentications — Configure
nsauditlogand forward to your SIEM. Alert on anySESSION_CREATEDevents that lack a correspondingAUTH_SUCCESSfrom your RADIUS/LDAP/SAML IDP. This is the primary detection signal for auth-bypass exploitation. Deploy immediately. - Rotate all credentials stored on the appliance post-patch — After patching, rotate: nsroot password, LDAP bind credentials in
ns.conf, SAML signing certificates, TLS private keys on all Gateway vservers, and any stored RADIUS shared secrets. Assume pre-patch compromise is possible. Complete within 7 days of patching. - Deploy IDS/IPS signatures for anomalous NetScaler auth flows — If your upstream IPS (Palo Alto, Fortinet, Snort) releases signatures for CVE-2026-19490, deploy them in blocking mode. Even generic 'NetScaler auth anomaly' rules provide partial coverage. Deploy within the 3-day mitigation window.
- WAF in front of NetScaler — The Gateway VIP typically terminates TLS itself; inserting a WAF between the internet and the Gateway breaks the VPN/ICA proxy flow and is not architecturally viable in most deployments.
- Disabling SAML or AAA features — While the prerequisite is Gateway/AAA vserver configuration, disabling these features effectively disables the product's core function (remote access), making this equivalent to taking the appliance offline rather than a true compensating control.
- NetScaler AppFirewall (built-in WAF) — The auth bypass occurs before the AppFirewall policy evaluation point in the NetScaler packet processing pipeline, so AppFirewall rules cannot intercept it.
Crowdsourced verification payload.
Run this script via SSH on each NetScaler appliance (requires nsroot or equivalent shell access). Example: ssh nsroot@<netscaler-ip> 'bash -s' < check_cve_2026_19490.sh. Requires shell access to the NetScaler BSD subsystem.
#!/bin/bash
# CVE-2026-19490 Version Check for NetScaler ADC / Gateway
# Run on the NetScaler appliance via SSH as nsroot
# Exit codes: 0=PATCHED, 1=VULNERABLE, 2=UNKNOWN
VERSION_FILE="/var/nsinstall/.version"
if [ ! -f "$VERSION_FILE" ]; then
# Try alternate location
VERSION_FILE="/var/nslog/install.log"
fi
# Get installed version
INSTALLED=$(nsapimgr_wr.sh -d version 2>/dev/null | grep -oP '\d+\.\d+-\d+\.\d+' | head -1)
if [ -z "$INSTALLED" ]; then
INSTALLED=$(cat /var/nsinstall/.version 2>/dev/null | grep -oP '\d+\.\d+-\d+\.\d+' | head -1)
fi
if [ -z "$INSTALLED" ]; then
echo "UNKNOWN - Could not determine NetScaler version"
exit 2
fi
echo "Detected NetScaler version: $INSTALLED"
# Parse major.minor-build.rev
MAJOR=$(echo "$INSTALLED" | cut -d'.' -f1)
MINOR=$(echo "$INSTALLED" | cut -d'.' -f2 | cut -d'-' -f1)
BUILD=$(echo "$INSTALLED" | cut -d'-' -f2 | cut -d'.' -f1)
REV=$(echo "$INSTALLED" | cut -d'-' -f2 | cut -d'.' -f2)
# Check if Gateway or AAA vserver is configured (prerequisite)
GW_CONFIG=$(nscli -U :nsroot:nsroot show vpn vserver 2>/dev/null | grep -c 'Name:')
AAA_CONFIG=$(nscli -U :nsroot:nsroot show authentication vserver 2>/dev/null | grep -c 'Name:')
if [ "$GW_CONFIG" -eq 0 ] && [ "$AAA_CONFIG" -eq 0 ]; then
echo "INFO: No Gateway or AAA vserver configured. Appliance may not be exploitable, but patching is still recommended."
fi
# Version comparison
# Fixed: 14.1-73.32+ or 13.1-63.21+
VULN=0
if [ "$MAJOR" -eq 14 ] && [ "$MINOR" -eq 1 ]; then
if [ "$BUILD" -lt 73 ]; then
VULN=1
elif [ "$BUILD" -eq 73 ] && [ "$REV" -lt 32 ]; then
VULN=1
fi
elif [ "$MAJOR" -eq 13 ] && [ "$MINOR" -eq 1 ]; then
if [ "$BUILD" -lt 63 ]; then
VULN=1
elif [ "$BUILD" -eq 63 ] && [ "$REV" -lt 21 ]; then
VULN=1
fi
elif [ "$MAJOR" -lt 13 ]; then
echo "UNKNOWN - Version $INSTALLED is EOL and may or may not be affected"
exit 2
else
echo "UNKNOWN - Unexpected version $INSTALLED"
exit 2
fi
if [ "$VULN" -eq 1 ]; then
echo "VULNERABLE - NetScaler $INSTALLED is affected by CVE-2026-19490"
exit 1
else
echo "PATCHED - NetScaler $INSTALLED is not affected by CVE-2026-19490"
exit 0
fiIf you remember one thing.
Sources
- Citrix Security Bulletin CTX696939
- NVD - CVE-2026-19490
- Censys Advisory — NetScaler Exposure Data
- watchTowr Labs — Citrix NetScaler Pre-Auth RCE Analysis
- Dark Reading — CitrixBleed-ing Again? NetScaler Under Attack
- CyberScoop — Citrix NetScaler Flaw Echoes CitrixBleed
- CERT-EU — Multiple Vulnerabilities in Citrix NetScaler
What defenders are saying.
Crowdsourced verification outputs.
Results submitted by users who ran the verification payload against their environment.