Citrix NetScaler scores 9.5: no known abuse is no reason to wait

Citrix published critical flaws in NetScaler ADC and Gateway, up to CVSS 9.5. There is no known exploitation yet, but the CCB asks organisations to patch immediately. Earlier NetScaler bugs were exploited quickly.

Glass entrance gate in front of a dark office building at night

For many SMEs, the Citrix NetScaler is the front door of remote work. Staff sign in through it, and the rest of the network sits behind it. On 12 November, Citrix published a bulletin with critical flaws in NetScaler ADC and Gateway. A day later, the Centre for Cybersecurity Belgium (CCB) urged organisations to patch immediately.

There is no known exploitation, and the flaws are not on the US CISA KEV list of actively exploited vulnerabilities. That is good news, not a reason to wait. Earlier NetScaler bugs, known as CitrixBleed in 2023 and 2025, were exploited quickly. The head start you have now is the time an attacker uses to test.

What's going on

In bulletin CTX697305, Citrix describes 28 vulnerabilities, mostly memory flaws. Two stand out.

CVE-2026-107412 scores 9.5 on the CVSS scale. It applies when NetScaler is configured as a Gateway (SSL VPN, ICA Proxy, CVPN or RDP Proxy) or as an AAA server, which authenticates users. For many companies, that is their remote access setup.

CVE-2026-120868 scores 9.3 and hits every NetScaler ADC and Gateway install on a vulnerable version, including the default configuration. No extra feature needs to be on. Anyone who thinks "we don't run Gateway, so this passes us by" is wrong about this one.

The exact impact needs care. Citrix describes both flaws as unpredictable or erroneous behaviour, or as denial of service: the appliance can hang or go down. The CCB writes that exploitation could disrupt remote access and the applications behind it. Other write-ups sometimes summarise 120868 as DoS alone. The scores remain critical, and the CVSS vector also rates high confidentiality and integrity impact. Citrix does not document code execution or data theft, and neither will we.

The rest of the bulletin depends on features such as DNS, SAML or the application firewall. Those need a configuration check, but they are lower priority.

Citrix reports no known exploitation, and there is no confirmed public proof of concept. The patches exist. For customer-managed appliances: 14.1-73.57 or later, 13.1-64.39 or later, and for FIPS or NDcPP variants 14.1-73.58 FIPS or 13.1-37.293 or later. Hybrid Secure Private Access with your own NetScaler instances is also in scope. Citrix-managed cloud services are updated by the vendor.

Why this belongs in the boardroom

A NetScaler that goes down is not an IT inconvenience. It is the day nobody can work from home, and the applications behind the Gateway stop.

Under NIS2, boards must show they manage risks like this. An official Belgian warning to patch immediately is hard to leave on the table. We said the same when the CCB asked organisations to update the Barracuda mail gateway at once: patch management is not IT housekeeping. It is liability.

As with the SonicWall VPN flaw, the door to the outside is the first thing an attacker looks for, and the last you want left untouched.

Through the attacker's eyes

At XPOSE, we think like the other side. What follows are scenarios, not a reconstruction of an attack and certainly not a how-to.

They already know this kind of front door. NetScaler has been on attackers' radar for years. CitrixBleed taught them that a flaw in this appliance pays off quickly. A new bulletin is a calendar item, not a surprise.

"No exploitation" is their working window. As long as the KEV list stays empty and the board still hears "test first, next maintenance evening", there is time. They will use it.

The default configuration is enough. CVE-2026-120868 needs no special feature. Check only the Gateway flaws and you miss the one that hits every install.

A door taken offline is also an attack. Not every campaign is after data. Sometimes it is enough to knock remote access down, as leverage, as a distraction, or as a first step. The CCB warns of that disruption.

The patch evicts no one. The CCB says it again, as it did with Barracuda: an update protects against future exploitation, but does not remediate a past compromise. Look back, not only ahead.

What to do today

  1. Patch to the fixed versions in CTX697305. 14.1-73.57 or later, 13.1-64.39 or later, or the FIPS and NDcPP builds named above. There is no workaround. Updating is the only path.
  2. Ask your MSP in writing: which version is running, when it was patched, and whether the appliance is a Gateway or AAA server, or an ADC in default configuration. The last case still counts for CVE-2026-120868.
  3. Step up monitoring and review the logs, as the CCB asks, for unexplained restarts, crashes or unusual access. A patch does not erase that trail.
  4. Do not kill active sessions by reflex. After CitrixBleed that was required, because sessions leaked. This bulletin does not require it. If you see something suspicious, end sessions and rotate credentials. A patch alone says nothing about who was already inside.
  5. Limit what is on the internet. The Gateway login page should not be more widely exposed than necessary, and the management interface should not be online at all. That does not replace the patch. Have someone check what of your environment is publicly visible.
  6. Do not forget the rest of the bulletin once the two critical flaws are closed: features such as SAML, DNS or the application firewall can leave further issues open.

Final thoughts

No known exploitation is the best moment to patch, not the moment to wait for the first victim. The patches are out, the CCB is clear, and NetScaler's history speaks for itself. The front door of remote work does not deserve delay.

XPOSE Security tests your environment the way real APT attackers would: from the Gateway login left online to the version that was "almost" updated. Better we find it than they do. Get in touch and strengthen your security posture structurally with our CISO as a Service.


Sources