28

CVEs in one NetScaler bulletin

9

scored 9.0 or higher under CVSS 4.0

9.5

top score, in the Gateway and AAA login path

4

fixed 14.1 builds since 2 Jul 2026

In a NetScaler bulletin, configuration decides exposure

A NetScaler bulletin with 28 CVEs is not 28 problems on every appliance. Each flaw in CTX697305 comes with a precondition, and the precondition decides whether your box carries it. Read the bulletin by configuration, not by count, and the patch order writes itself.

That matters because the count is what makes the news. Citrix published CTX697305 on 12 Nov 2026 and listed nine CVEs scored 9.0 or higher under CVSS 4.0. A team that reads "nine critical NetScaler bugs" will either panic or, more often, decide that a bulletin describing memory overflows with "unpredictable or erroneous behavior or Denial of Service" can wait for the next change window. Both responses skip the useful step.

Our argument has two parts. First, every NetScaler that terminates remote access as a Gateway or an AAA virtual server carries the worst of this bulletin, and it is the appliance most exposed to the internet, so it gets upgraded first. Second, the words "denial of service" in a NetScaler description should not lower anyone's priority. Citrix's own CVSS vectors score all nine critical flaws as high impact on confidentiality and integrity, not only availability. In September, a NetScaler memory overflow of the same class was used against customers before most of them had patched.

We covered the last big NetScaler memory leak in CitrixBleed 3. This bulletin is different in shape. There is no single headline bug, just a wide spread of overflows across features, which is exactly the kind of bulletin that gets triaged badly.

What Citrix disclosed in CTX697305

CTX697305 covers customer managed NetScaler ADC and NetScaler Gateway. Citrix rates the bulletin critical and lists 28 CVEs. All but one are memory safety flaws: buffer overflows on the stack and the heap, out of bounds writes and a double free. The exception, CVE-2026-111338, writes sensitive authentication material to a log file that a local user can read.

The fixed builds are 14.1-73.57, 13.1-64.39, 14.1-73.58 FIPS, and 13.1-37.293 for FIPS and NDcPP. Citrix notes that Secure Private Access hybrid deployments that use NetScaler instances are affected too, and that it upgrades the Citrix managed cloud services itself. Its only instruction to customers is to install the updated versions "as soon as possible". The bulletin offers no workaround and says nothing either way about exploitation.

CTX697305 Critical
  • Product //

    NetScaler ADC and NetScaler Gateway, customer managed
  • CVEs //

    28, nine scored 9.0 or higher under CVSS 4.0
  • Top score //

    9.5, CVE-2026-107412, Gateway or AAA virtual server
  • Default config //

    CVE-2026-120868 affects every deployment, 9.3
  • Fixed in //

    14.1-73.57, 13.1-64.39, 14.1-73.58 FIPS, 13.1-37.293 FIPS and NDcPP
  • Exploited //

    Not stated by Citrix

The nine critical entries are worth naming, because each one maps to a feature:

  • CVE-2026-107412, 9.5: multiple memory overflows when the appliance is a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual server.
  • CVE-2026-120868, 9.3: packet processing, in every deployment, with no additional feature required.
  • CVE-2026-120864, 9.3: the ICA proxy, on a Gateway VPN virtual server, an AAA virtual server or a CR virtual server of type HDX.
  • CVE-2026-111334, 9.3: Endpoint Analysis, on a VPN or AAA virtual server with EPA configured.
  • CVE-2026-107415, 9.3: Email OTP authentication, wherever an Email action is configured.
  • CVE-2026-107407, CVE-2026-107408, CVE-2026-107409 and CVE-2026-107410, all 9.3: SMPP load balancing, DNS recursive resolution, DNS over HTTPS (the double free) and NetScaler Push.

Below those sit fourteen flaws scored from 8.3 to 8.7 in SAML, WebAuth, LDAP, knowledge based and certificate authentication, HTTP/2, HTTP/3, TLS, base64 decoding in policy expressions, GSLB, several load balancing protocols and the management plane. The remaining five are lower scored local or adjacent issues, including a BGP flaw that requires the attacker to be, or spoof, a routing neighbor.

NVD published the records on 13 Nov 2026 and had not analysed them at the time of writing. The vector Citrix assigned to CVE-2026-120864 is network reachable, low complexity, no privileges and no user interaction.

Citrix also says its own product security team found several of the flaws "through advanced AI-assisted code analysis". Hold on to that line. It comes back in the last section.

Why "denial of service" should not lower the priority

Read the descriptions alone and most of CTX697305 sounds like an availability problem. "Memory overflow in ICA proxy can lead to unpredictable or erroneous behavior or Denial of Service" is the NVD text for CVE-2026-120864. On a perimeter appliance, a crash is already serious: the Gateway is how remote staff reach the business.

The scores say more than the sentences. In the bulletin's own CVSS 4.0 vectors, all nine critical flaws carry high impact on confidentiality and integrity as well as availability. The fourteen flaws scored 8.7 or 8.3 carry high impact on availability with no more than low impact on the other two. That is the split we would use to order the work, because it is Citrix's own judgement of which bugs are more than an outage.

The September bulletin shows why. CTX697096, published 27 Sep 2026, fixed eight CVEs. One of them, CVE-2026-88772, is described as a "Memory overflow vulnerability leading to Remote Code Execution or Denial of Service" when DTLS is enabled, which the bulletin notes is on by default on a VPN virtual server. Citrix wrote in the same bulletin that "Exploits of CVE-2026-88771 and CVE-2026-88772 on unmitigated NetScaler deployments have been observed." The bug class in November is the same: memory overflow in a network facing parser on the appliance that terminates remote access.

We are not saying any CTX697305 flaw is being exploited. Citrix has not said so, and nobody else we can source has either. We are saying the descriptions are not the place to look for the risk, and the history of this product does not reward waiting.

Figure 01

Four NetScaler fixed builds since July

  1. //

    SIX CVES

    CSA Singapore publishes an alert for six NetScaler flaws, fixed in 14.1-72.61 and 13.1-63.18.

    Watch

    appliances still below 14.1-72.61 carry every bug since

  2. //

    AUTH BYPASS

    CTX696939 fixes CVE-2026-19490, a 9.3 authentication bypass on Gateway and AAA virtual servers. Fixed in 14.1-73.32 and 13.1-63.21.

    Watch

    Gateway logins that never passed authentication

  3. //

    EXPLOITED

    CTX697096 fixes eight CVEs; Citrix says two were exploited on unmitigated appliances. Fixed in 14.1-73.37 and 13.1-64.23.

    Watch

    compromise that predates the September upgrade

  4. //

    28 CVES

    CTX697305, nine scored 9.0 or higher. Fixed in 14.1-73.57 and 13.1-64.39.

    Watch

    Gateway and AAA appliances below 14.1-73.57

  5. //

    PUBLIC RECORDS

    NVD publishes the CVE records.

    Watch

    new scanner signatures and public analysis of the fixed builds

Four fixed 14.1 builds in about four and a half months, and the Gateway and AAA role appears in all four bulletins.

The timeline has two practical consequences. The Gateway and AAA role keeps coming up: an overflow on Gateway and AAA virtual servers in July, CVE-2026-19490 in August, the DTLS flaw on VPN virtual servers in September, and the worst of November. And an appliance that skipped September and upgrades today closes every bulletin since July in one move, but it also spent seven weeks exposed to two flaws Citrix says were used in attacks. That appliance needs a look for compromise, not just a new build.

Which NetScaler configurations are exposed

The bulletin is unusually helpful here. For every CVE, Citrix gives the precondition and a check: a configuration line to search for in the running config. That turns 28 CVEs into a short list per appliance.

Figure 02

The role of the appliance decides which of the 28 it carries.

EVERY NETSCALER

CVE-2026-120868, default config

  • GATEWAY OR AAA

    the 9.5 plus ICA proxy

  • EPA OR EMAIL OTP

    two more at 9.3

  • DNS, SMPP, PUSH

    four at 9.3

  • MANAGEMENT IP

    reachable from untrusted hosts

Start from the role: a remote access Gateway carries the worst of the bulletin, and every feature switched on after that adds to the list.

Four roles cover most real estates.

Every appliance. CVE-2026-120868 sits in packet processing and needs no feature. There is no configuration that removes it. Every NetScaler you own is in scope for at least one 9.3.

Remote access. An appliance configured as a Gateway or an AAA virtual server picks up CVE-2026-107412 at 9.5 and CVE-2026-120864 at 9.3, plus an LDAP authentication overflow and a local authentication request flaw. If Endpoint Analysis is configured, add CVE-2026-111334. If Email OTP is in use, add CVE-2026-107415. SAML, WebAuth, knowledge based and certificate authentication each add an 8.7. A typical remote access Gateway with EPA and SAML carries four of the nine critical flaws before anyone looks at load balancing.

Load balancing and DNS. The other four critical flaws are tied to specific virtual server types and features: SMPP, DNS load balancing with recursive resolution, DNS over HTTPS and Push. Many ADC deployments use none of them. Some use DNS heavily. The config check tells you which.

Management. CVE-2026-120863 needs an untrusted host to reach the appliance's management address, NSIP or NSIP6. It scores 8.7 and is availability only, but it is the cheapest one to close. A management interface reachable from an untrusted network is a finding on its own, as we set out in our exposed admin and debug endpoint checks.

The point of the map is ordering, not exemption. Every supported build below the fixed version carries CVE-2026-120868, so every appliance gets the upgrade. The map tells you which appliance goes tonight and which goes this week.

How to check a NetScaler appliance before and after the upgrade

Start with the inventory. List every NetScaler instance you run, including the ones that do not belong to the network team: the HA secondary, the disaster recovery pair, the appliance a project stood up for one application, and any instances behind Secure Private Access hybrid. Record the build and whether it is FIPS or NDcPP, because those have their own fixed builds.

Then run the bulletin's checks against each running configuration. They are plain text searches. A Gateway shows a line beginning add vpn vserver. An AAA virtual server shows add authentication vserver. Endpoint Analysis shows add authentication epaAction. SAML shows add authentication samlAction. The bulletin lists the equivalent check for each of the 28, including the load balancing types, HTTP/2 and HTTP/3 profiles, GSLB settings and the BGP neighbor condition. Save the output per appliance. It is your evidence for why each box was ordered the way it was.

Then order the work:

  1. Internet facing Gateway and AAA appliances, whatever else they run.
  2. Any appliance with DNS recursive resolution, DNS over HTTPS, SMPP or Push virtual servers.
  3. Everything else, which still carries CVE-2026-120868.

While you wait for a window, cut what you can. Restrict the management addresses to a management network. Remove virtual server types and authentication actions nobody uses; an Email OTP action left over from a pilot is now a 9.3 on the login page. These steps reduce exposure. They are not a fix, and Citrix lists no workaround.

After the upgrade, confirm the build on every node, not only the primary of a pair. Then look backwards. Any Gateway that sat below 14.1-73.37 or 13.1-64.23 after 27 Sep was exposed to the two flaws Citrix says were exploited, so review it as a possible compromise: unexpected files in the web directories, new administrator accounts, configuration changes nobody made, and unusual outbound connections from the appliance itself. A new build does not remove anything an attacker left behind. We made the same point about firewalls in the Check Point PHP2Shell breakdown: patching closes the hole and leaves the implant.

Finally, plan for the sessions. A Gateway holds live remote access sessions and the credentials that pass through its login page. If the review finds anything, end active sessions and rotate the service and administrator credentials the appliance holds after the rebuild, not before.

How we test NetScaler on an engagement

On an external test, the first job is finding every NetScaler the client exposes, including the ones that are not on the asset list. We work from the client's domains, certificates and address ranges, the method in our external recon guide, and atarus-recon on our open source page covers the same ground. Gateway login pages and management interfaces have distinct fingerprints, and an appliance stood up for one project and forgotten is a common find.

For each one we record what it answers on: the Gateway login page, any AAA login page, the authentication methods it offers, and whether a management interface responds from the internet. That maps directly to the preconditions in CTX697305. A login page that offers Email OTP tells us one more critical flaw applies before we ask for a single config line.

We do not fire memory corruption bugs at a production NetScaler. A crash takes remote access down for the whole company, and a failed attempt against a heap overflow can leave the appliance in a worse state than either outcome the client wanted to learn about. We confirm the build and the configuration with the client, report the exposure, and test the blast radius from a position we are given.

That last part is where the real finding usually is. On an assumed breach or internal engagement we ask what a compromised Gateway would reach. It sits on both sides of the perimeter by design. It talks to the directory for LDAP authentication, it holds certificates and service credentials, and it usually has routes to the application servers it publishes. We map those paths and check whether the appliance's own credentials work anywhere else. The appliance is the one host an attacker most wants, because it is trusted on the way in and trusted on the way out.

We also look at the patch history as its own finding. How long did the September and July builds take to land? Who decides when the remote access appliance gets a maintenance window? Is the HA secondary on the same build? A NetScaler estate that is one build behind is normal. One that is four builds behind, still below 14.1-72.61, is carrying every flaw since July.

What is still coming

Expect public analysis of the fixed builds. When a vendor fixes 28 memory safety bugs in one release, researchers compare the old and new code, and the first detailed write ups of what changed tend to follow within days. NetScaler has drawn that attention before.

Expect more bulletins of this size. Citrix says its own team found several of these flaws with AI assisted code analysis. The defenders' side of that coin is more fixes in a single release. The attackers' side is that the same tools can read the fixed builds, so the time between a bulletin and a working exploit is shrinking. Plan for bulletins with dozens of CVEs and for less time to act on them.

Expect scanner signatures to lag the preconditions. Most vulnerability scanners will flag every appliance below the fixed build, which is correct for CVE-2026-120868 and says nothing about which of the other 27 apply. The configuration checks are your own job.

And expect this bulletin to stay relevant for a while. NVD had not finished its analysis when we published, Citrix had not commented on exploitation, and the appliances that skip this cycle will carry these flaws into the next one.

What to do today

  1. Upgrade every internet facing Gateway and AAA appliance tonight. 14.1-73.57, 13.1-64.39, 14.1-73.58 FIPS or 13.1-37.293 for FIPS and NDcPP. Both nodes of every pair.

  2. Run the CTX697305 configuration checks on every appliance. Save the output and use it to order the rest: DNS, SMPP and Push virtual servers next, everything else after, since CVE-2026-120868 applies to all of them.

  3. Close the management plane. NSIP and NSIP6 should only answer on a management network. That removes CVE-2026-120863 and much else besides.

  4. Remove what nobody uses. Unused Email OTP, EPA, SAML and load balancing virtual servers each add flaws from this bulletin.

  5. Review any Gateway that sat below the September build. Below 14.1-73.37 or 13.1-64.23 after 27 Sep means it was exposed to two exploited flaws; look for changes nobody made before you trust it.