Safeguard
Vulnerability Analysis•

NetScaler in CISA KEV Three Times in Four Weeks: What to Patch

CISA added four NetScaler ADC and Gateway CVEs to KEV between 9 September and 4 October 2026, two of them unauthenticated RCE. Builds, checks and IR steps.

Safeguard Security Team
6 min read

Between 9 September and 4 October 2026, CISA added four Citrix NetScaler ADC and NetScaler Gateway vulnerabilities to its Known Exploited Vulnerabilities catalog across three separate updates. The most serious pair, CVE-2026-88771 and CVE-2026-88772, went in on 27 September with a federal due date of 30 September. Citrix says exploits of both have been observed on unmitigated deployments.

If you patched in early September and stopped there, you are still exposed. Each bulletin raised the minimum safe build.

What's affected

The four KEV entries:

CVEKEV addedDueWhat it isPrecondition
CVE-2026-194909 Sep12 SepAuthentication bypass, CVSS 4.0 score 9.3Gateway or AAA virtual server, SAML action on newer builds
CVE-2026-8877127 Sep30 SepUnauthenticated command execution, 9.5Every deployment, default config
CVE-2026-8877227 Sep30 SepMemory overflow, RCE or DoS, 9.5DTLS enabled, on by default for VPN vServers
CVE-2026-887794 Oct7 OctMemory overflow, DoS, 8.7Configured as SAML SP or SAML IdP

CVE-2026-88771 and CVE-2026-88772 come from bulletin CTX697096, which also covers six more CVEs (88773 to 88778), including HTTP request smuggling and TCP sequence number prediction. Those six are not in KEV, but the same upgrade fixes them, except CVE-2026-88778, which also needs a TCP setting change.

Fixed builds, by bulletin:

LineCTX696939 (19490)CTX697096 (88771, 88772)CTX697174 (88779)
14.114.1-73.3214.1-73.3714.1-73.41
13.113.1-63.2113.1-64.2313.1-64.28
14.1 FIPS14.1-73.32 FIPS14.1-73.37 FIPS14.1-73.41 FIPS
13.1 FIPS and NDcPP13.1-37.27713.1-37.27913.1-37.282

The right-hand column is the one to target. 14.1-73.41 or 13.1-64.28 and later cover all four KEV entries. Secure Private Access hybrid deployments that use NetScaler instances are affected too. Citrix-managed cloud services are updated by Citrix.

How to check if you're exposed

From the NetScaler CLI, get the build:

show ns version

Then check the preconditions against your saved config, using the patterns from Citrix's bulletins. From the shell:

# CVE-2026-88772: VPN vservers without "-dtls OFF" have DTLS on by default
grep -E '^add vpn vserver' /nsconfig/ns.conf | grep -v -- '-dtls OFF'
grep -E '^add (vpn|lb) vserver .* DTLS ' /nsconfig/ns.conf

# CVE-2026-19490 and CVE-2026-88779: Gateway, AAA and SAML config
grep -E '^add (vpn|authentication) vserver' /nsconfig/ns.conf
grep -E '^add authentication (samlAction|samlIdPProfile)' /nsconfig/ns.conf

For CVE-2026-88778, Citrix's check runs from the CLI and flags appliances where Enhanced ISN Generation is disabled:

show ns tcpparam | grep "Enhanced ISN Generation"

CVE-2026-88771 has no precondition. Citrix says every NetScaler ADC and Gateway deployment is affected, including the default configuration. So the build number alone decides exposure for the most serious bug.

For hunting, CISA's KEV notes say running the IOCs Citrix provides in the NetScaler console may help identify exploitation, and they direct customers to conduct forensic triage. Citrix's indicators are published in its community blog for the 88771 to 88778 bulletin.

What to do now

  1. Upgrade to 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS or 13.1-37.282 or later. That clears all four KEV entries in one change.
  2. Apply the Enhanced ISN Generation setting from Citrix's TCP configuration docs if show ns tcpparam reports it disabled.
  3. Run Citrix's IOC checks on every appliance that was internet facing before you patched. Patching does not remove an implant.
  4. If anything looks wrong, follow Citrix's CTX694799 steps. For a VPX, snapshot it and document system time and NTP settings. Generate a support bundle and a Packet Engine core dump, then isolate the device.
  5. After a suspected compromise, rotate everything the appliance stored. Citrix lists LDAP service accounts, RADIUS shared secrets, OAuth tokens, API keys and SNMP community names. Revoke the appliance's certificates and private keys, and change passwords for users who authenticated through it.
  6. Rebuild rather than clean. Citrix recommends replacing and restoring VPX instances and reimaging MPX appliances, then upgrading firmware before restoring a backup that predates the compromise.

Why it matters

Edge appliances keep showing up in KEV because they sit on the internet, terminate authentication and hold credentials for the network behind them. Four NetScaler entries in under a month is not unusual for this product class. It does mean a monthly patch cycle is too slow for it.

The table above is the practical lesson. Each bulletin's "fixed" build was superseded within weeks. Track the latest fixed build per product line, not per CVE, and re-check after every new bulletin.

Try it yourself

Pull show ns version from every NetScaler you run, including lab and DR units, and compare each against 14.1-73.41 or 13.1-64.28. Then search each saved config for add vpn vserver lines without -dtls OFF. That gives you an exposure list in a few minutes.

This demo shows how continuous monitoring flags a newly exploited CVE against assets you already track:

Click through it at your own pace, or open it full screen.

Quick check

Does disabling DTLS protect against CVE-2026-88771?

No. DTLS is the precondition for CVE-2026-88772. Citrix says CVE-2026-88771 affects all deployments with the default configuration, so only the upgrade fixes it.

I upgraded to 14.1-73.37 after the 27 September bulletin. Am I covered?

Not for CVE-2026-88779. Its bulletin lists 14.1-73.41 as the first fixed 14.1 build.

Do I need to do anything for Citrix-managed cloud services?

Citrix says it upgrades Citrix-managed cloud services and Citrix-managed Adaptive Authentication itself. The bulletins apply to customer-managed appliances.

Sources

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.