Latest

Cybersecurity

NetScaler CVE-2026-120868 affects all of Citrix by default

CVE-2026-120868 affects any ADC or Gateway in the default configuration and requires no authentication; Console adds an authentication bypass scoring 9.4.

NetScaler CVE-2026-120868 affects all of Citrix by default
NetScaler CVE-2026-120868 affects all of Citrix by default

Cloud Software Group published the NetScaler security bulletins on November 12, 2026, and closed 28 vulnerabilities in ADC and Gateway in one go, plus another in Console. The figure is less impressive than a single line from the Citrix NetScaler ADC and Gateway security bulletin: CVE-2026-120868 scores 9.3 out of 10 and affects every deployment, including those that never left the factory configuration.

The rest of the list competes in another category. The other 27 flaws require someone to have previously enabled a very specific feature of the appliance, whether SAML authentication, HTTP/3 load balancing or the ICA proxy for desktops. The 9.3 one needs none of that, asks for no credentials and does not wait for anyone to click. The highest-scoring one, CVE-2026-107412 with 9.5, instead stops short of anyone who has the device configured as a Gateway or as an authentication virtual server. For the 9.3 there is no published workaround, so the only remediation is the patched version.

Two days after publication, no one has documented exploitation of these flaws and there is no public proof of concept. The CERT-EU alert notes that absence and calls for starting with the Gateway and AAA appliances that face the internet.

The flaw that asks no permission

The mechanism is a memory overflow in packet processing, classified CWE-119 within the family of writes that run past buffer bounds. Citrix describes the vector as network-reachable, without privileges and without user interaction, and the outcome it signs off on in the text is erratic behavior or denial of service. Translated: a malformed packet can take down the appliance holding the session of thousands of remote workers.

The scorecard and the text do not say exactly the same thing, and that gap deserves attention. The bulletin speaks only of crashes, but the scoring vector marks high impact on confidentiality and integrity as well as on availability. The vendor does not rule out those consequences in writing, nor does it describe them. With that ambiguity, the 9.3 reads as an availability flaw with a ceiling we do not yet know, not as a demonstrated code execution.

Here is the distinction that orders the patch queue. A configuration-dependent vulnerability exists only if someone enabled the feature that exposes it; a universal one depends on no decision by the administrator on duty. CVE-2026-120868 belongs to the second group and that is why it weighs more than the 9.5, which lives inside the Gateway or AAA configuration.

The practical consequence is uncomfortable: no checklist saves anyone. A freshly installed appliance, without a single directive added, already meets the precondition for the most serious flaw in the batch.

Which flaws affect each appliance?

Citrix added each CVE's precondition to the bulletin alongside the configuration pattern that reveals it, and that annex turns the inventory into a text-search exercise. The Beazley Security analysis recommends exporting each appliance's ns.conf file and comparing it against those patterns before deciding where to start. The table summarizes the six highest-reach cases.

CVE CVSS v4.0 What has to be enabled String that reveals it in ns.conf
CVE-2026-120868 9,3 Nothing, the default configuration is enough None: affects all appliances
CVE-2026-107412 9,5 Gateway or AAA virtual server `add vpn vserver` and `add authentication vserver`
CVE-2026-120864 9,3 ICA proxy in Gateway, AAA or HDX-type CR `add cr vserver <name> HDX`
CVE-2026-111334 9,3 Endpoint analysis in VPN or AAA `add authentication epaAction`
CVE-2026-120860 8,7 Diameter, MQTT or RADIUS load balancing `add lb vserver <name> DIAMETER`
CVE-2026-120863 8,7 NSIP management reachable from outside The administration address itself

Reading the table leaves a small, verifiable relief. A device that only balances HTTP and has neither SAML nor Gateway appears in just one of the six rows, the first. The same device remains exposed to packet overflow, because that flaw does not ask which features are turned on, and that is why the patch order is set by configuration and not by score.

Here is what really separates this batch from a routine update. The rest of the list punishes features that many administrators do not even remember having active, and each one adds its own risk to the organization's inventory:

  • 8.7 in SAML, WebAuth, LDAP, RADIUS, MQTT, GSLB with metric exchange and client certificate.
  • 8.7 in HTTP/3 over QUIC and in the management plane exposed by the NSIP address.
  • 7.7 in dynamic BGP without TCP-MD5 authentication, with the added condition of being the configured neighbor.

Authentication is the part that weighs most in practice. A device that terminates VPN sessions and asks for a second factor sits on the business's critical path, and the flaws that slip through there have precedent: the MFA bypass in SonicWall's VPN showed how costly it is to leave the remote access door unpatched.

Console is the park's gateway

The day's second bulletin has its own story. CVE-2026-120869 lives in NetScaler Console, the console from which an entire fleet of devices is administered, and scores 9.4 out of 10 for improperly implemented authentication, CWE-287. The Console advisory says an attacker without credentials can bypass controls and reach restricted resources on the device. It was found by Cloud Software Group's product security team through artificial intelligence-assisted analysis.

The nuance lies in the vector. The score uses AV:A, adjacent network, not AV:N, so exposure depends on where the console is installed and who can reach it. A Console instance inside an administration network is not the same as another mistakenly published on an internet-facing interface, and the vector itself also grants high impact on the systems that depend on it.

The version that closes the gap is Console 14.1-74.34, and it ships in a different package from the devices. Anyone with the fleet on 14.1-73.57 and the old console still has the door open.

The potential damage is second-order, which is why it is concerning. Console administers the devices, stores their credentials and distributes configurations, so an authentication bypass there turns a breach into a remote control over the entire fleet. The same logic appeared in the cookie that gave root in Xen Orchestra, with the flaw sitting one level above the system that was worth attacking.

The patch that cuts people's sessions

Updating is not downloading and restarting. Beazley Security's analysis recalls that both nodes of each high-availability pair must be upgraded, because the cluster is left limping if only one is touched, and that the update terminates active ICA sessions. In a hospital or an accounting firm with shifts, that is a maintenance window to be negotiated, not a click in the early hours.

The risk window does not close with the patch installed either. The same analysis notes that memory flaws in NetScaler became exploitation material within days during the autumn of 2026, with webshells planted on compromised devices, because attackers compare patched and unpatched versions. With 28 new identifiers in circulation there is more than enough material for that comparison. The chain that ended in root on PAN-OS firewalls shows how far a well-exploited perimeter flaw can go, and here the perimeter is the same one that distributes remote access for half of the business world.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading