Citrix Patches 10 Critical NetScaler Vulnerabilities — and a Secure Access Client Flaw That Hands Users SYSTEM

Citrix Patches 10 Critical NetScaler Vulnerabilities — and a Secure Access Client Flaw That Hands Users SYSTEM

Citrix Patches 10 Critical NetScaler Vulnerabilities — and a Secure Access Client Flaw That Hands Users SYSTEM

Citrix's November security update for NetScaler is bigger than the headline suggests. Announced November 11 and fleshed out across the week, the bulletin covers 12 vulnerabilities across NetScaler ADC, NetScaler Gateway, NetScaler Console, and the Secure Access Client — ten of them rated critical, all of them memory-corruption flaws in packet-processing paths, and one of them, CVE-2026-120868 (CVSS 9.3), affecting every NetScaler ADC and Gateway deployment regardless of configuration. Citrix says it is not aware of active exploitation of any of the announced flaws, but the company's own history — and this year's NetScaler zero-day cadence — makes "not yet" the operative phrase.

The critical list reads like a map of protocol-handling corners: memory overflow in Packet Processing (CVE-2026-120868, all deployments), in SMPP traffic handling (CVE-2026-107407, CVSS 9.3), in DNS and DNS-over-HTTPS (CVE-2026-107408 and CVE-2026-107409, both 9.3, for DNS load-balancing configurations), in NetScaler Push (CVE-2026-107410), in Gateway/AAA virtual servers (CVE-2026-107412, CVSS 9.5), in Email OTP authentication (CVE-2026-107415), in Endpoint Analysis (CVE-2026-111344), and in ICA proxy (CVE-2026-120864). Two further high-severity issues — an authentication bypass in the Secure Access Client for macOS (CVE-2026-120869) and a privilege-management flaw in the Windows client (CVE-2026-118268) that lets a low-privileged user escalate to SYSTEM — round out the set. The fixes ship in NetScaler ADC and Gateway 14.1-73.57 and later, 13.1-59.19 and later, and 13.0-92.23 and later, with Console patched in 14.1-74.34+.

Context makes this batch urgent rather than routine. Citrix published a support article in October specifically warning customers to prepare patch pipelines for frequent NetScaler updates — an unusually candid acknowledgment that these appliances are under continuous attack. Most of these flaws require specific virtual-server configurations to be exposed, but the packet-processing issue applies universally, and NetScaler appliances sit at the exact layer (internet-facing load balancing and VPN termination) where reachability is the default. The pattern of memory corruption in protocol parsers is also the same class that turned previous Citrix bugs into mass-exploitation events, so the absence of in-the-wild reports today should set your patch deadline, not relax it.

What Should You Do?

  1. Update to the fixed builds on all NetScaler ADC and Gateway appliances — 14.1-73.57+, 13.1-59.19+, or 13.0-92.23+ — prioritizing internet-facing Gateway and AAA virtual servers first.
  2. Map the config-specific flaws to your actual setup: SMPP load balancing, DNS/DoH resolution, Push services, Email OTP, EPA scans, and ICA proxy each unlock a different CVE — a five-minute virtual-server inventory tells you which of the ten criticals you actually face.
  3. Patch NetScaler Console too (14.1-74.34+) — the management plane is frequently forgotten while the data plane gets patched.
  4. Push the Secure Access Client updates to endpoints — the Windows privilege-escalation flaw (CVE-2026-118268) means unpatched remote-access clients hand local attackers SYSTEM, which is a foothold no gateway patch can undo.

The WAF Angle

NetScaler is often the WAF in an organization — ADC and Gateway ship Citrix's own application firewall — so this bulletin is a reminder that the security appliance is itself a protocol-parsing application with a memory-corruption attack surface. Ten critical memory bugs in one release, spread across parsers for SMPP, DNS, DoH, ICA, and authentication flows, is precisely the kind of surface a WAF rule engine normally protects web apps from — but nothing protects the parser inside your own appliance. Two practical moves follow. First, exposure minimization: every protocol feature you don't use (Push, SMPP, Email OTP) is pure attack surface, and disabling unused virtual-server types shrinks the critical list for free. Second, if a third-party WAF sits in front of Citrix-hosted services, treat memory-corruption advisories as virtual-patch triggers the day they publish, not after KEV — as we saw when three chained Ivanti zero-days gave attackers root on a fully patched appliance, edge devices are the new web apps, and their patch cadence is your defense.

Sources