Citrix NetScaler's November fixes: one flaw hits every box, and Console has a login bypass
Citrix fixed 28 flaws in NetScaler ADC and Gateway on November 12, and one hits every appliance in its default setup. NetScaler Console has a login bypass. Here's what each one means, the fixed builds and what to do this week.
part 40 of 43 · Platform releases, explained from scratchthe ideaOne NetScaler flaw hits every default setup. Patch the Gateway and fence the rest.
after reading, you can- Work out which of the 28 NetScaler flaws apply to each of your appliances, using Citrix's own config checks
- Find the fixed build for each NetScaler line you run, and upgrade an HA pair in the right order
- Close the management address and NetScaler Console to strangers while the upgrades go through
Citrix put out four security bulletins for NetScaler on November 12. The big one covers 28 flaws in NetScaler ADCdefinitionIt's the same box, used as a load balancer. Traffic for a website or app hits it first and gets shared out across several servers, and it usually handles the TLS encryption too. and Gateway, and one of them affects every appliance, even with the default configuration. If you run NetScaler yourself, book the firmware upgrade for this week and check that the NetScaler Console login page and the management addresses can't be reached from the internet.
The box that lets your staff in from home has a long list of new holes, and some need no password.
NetScaler Gateway is the front door many companies use for remote access. Staff sign in through it to reach the VPN, virtual desktops or internal web apps. NetScaler ADC is the same appliance doing load balancing, spreading traffic across servers. Citrix has now found memory bugs in the code that reads all of that traffic. Someone who never logs in can set off several, and nine of them score 9.0 or more out of 10. A separate bug lets an outsider who can reach NetScaler Console get past its login. Console is the tool admins use to manage all their NetScaler boxes. Fixed firmware is out for every supported line.
Think of the security desk in your building's lobby, where everybody checks in first. Citrix found that some odd requests confuse the person at the desk. Sometimes they just stop working, and nobody can be sure what else a confused desk might do. A fault at that desk hurts more than one in a back office, because every visitor walks past it.
- Firms whose staff log in through a Gateway
- Teams load balancing apps on NetScaler ADC
- Admins with an on-premises NetScaler Console
- Citrix Virtual Apps and Desktops shops
Why it matters to you
A NetScaler GatewaydefinitionCitrix's remote-access appliance. Staff sign in through it to reach the VPN, virtual desktops or internal web apps, so it sits on the internet by design. sits on the internet on purpose. Its whole job is to answer strangers and decide who gets in. So a flaw that needs no login and works on the default configuration is about as exposed as a bug can be. If the Gateway goes down, remote staff can't work. If an attacker gets further than a crash, they're standing at the door to your internal network.
Citrix calls most of these memory overflows that "can lead to unpredictable or erroneous behavior or Denial of Service". That reads mild. The scores don't. All eight of the ones rated 9.3 are scored high for confidentiality, integrity and availability, which is how a scorer marks a bug that could do more than knock the box over. Citrix hasn't said anyone is using them, and none were on CISA's Known Exploited Vulnerabilities list in the catalog CISA released on November 13.
History is the reason to move fast anyway. CISA has added six NetScaler flaws to that list this year: one in March, one in August, three in September and one on October 4. At least three of them were memory-buffer bugs, the same family as most of this batch. Attackers clearly watch NetScaler bulletins, and the gap between a fix and an exploit has been short.
How the attacks work
-
01 Finds a NetScaler that answers
Gateways and load-balanced sites face the internet by design. Scanners list them by the login page or the TLS certificate.
-
02 Sends a malformed request
They don't need an account. They aim at something the box has switched on, like SAML sign-in, Email OTP or DNS, or at the packet handling every box runs anyway.
-
03 Memory gets overwritten
The code copies more data than the buffer can hold, or frees the same memory twice. What happens next depends on the bug and the build.
-
04 The box crashes or misbehaves
At best the appliance restarts and remote access drops. Citrix also lists one flaw that can put it in a reboot loop.
-
05 Worse if it goes further
Citrix doesn't say any of these run code. The high integrity scores mean it can't be ruled out, and a Gateway sits right in front of the internal network.
For engineers: CVE-2026-120868 is the one that hits every deployment. Citrix lists it as a memory overflow in packet processing (CWE-119), scored 9.3, with the precondition "Default configuration / No additional feature required". The others depend on what you've configured. CVE-2026-107412, the 9.5, is several memory overflows reachable whenever the box runs as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual serverdefinitionThis is the bit of NetScaler that does the sign-in. Before anyone gets through to an app, it checks them against SAML, LDAP, RADIUS or whatever else you've set up.. Its vector has attack requirements present, so it needs some condition to line up, and it's scored high on the systems behind the box as well.
The identity features take a big share of this batch. There are separate overflows in SAML actions, WebAuth, Email OTP, knowledge-based authentication, client-certificate authentication, LDAP authentication and Endpoint Analysis. If your Gateway signs people in through Microsoft Entra ID or Okta over SAML, or checks passwords against Active Directory over LDAP, at least two of these apply to you on top of the default-config bug.
What Citrix fixed, and on which builds
The flaws that matter most in the November bulletins
This is CVE-2026-120868, at 9.3, and nobody has to log in to use it. A NetScaler left on its default configuration is exposed, ADC or Gateway. You don't have to switch anything on to be affected.
CVE-2026-107412 needs no login. It applies whenever the box is a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual server.
The worst two are in Email OTP (CVE-2026-107415) and Endpoint Analysis (CVE-2026-111334), both at 9.3. The SAML, WebAuth, KBA, client-certificate and LDAP ones sit at 8.7, which still needs no login.
CVE-2026-120864 scores 9.3 and needs no login. You're in scope if you run a Gateway VPN or AAA virtual server, or a CR virtual server of type HDX.
Each scores 9.3 and only applies if you run that kind of virtual server. Check for SMPP, DNS recursion, DNS over HTTPS or PUSH virtual servers.
CVE-2026-120863 scores 8.7 and needs no login. Anyone on an untrusted host who can reach the management IP can trigger it. A firewall in front of the NSIP cuts down who can try it.
CVE-2026-111338 only scores 6.9, but don't skip it, because it's about credentials. Once anyone has logged out, sensitive sign-in data can end up in /var/log/httperror.log. Someone with local read access on the box could pick it up from there.
CVE-2026-120869 needs no login. The bulletin scores it 9.4 and the NVD record 9.3. Fixed in Console 14.1-74.34. Only 14.1 is listed, since Console 13.1 reached end of life in April.
Both score 8.5. A standard user on the laptop can make themselves SYSTEM or root. Fixed in 26.11.1.6 for Windows and 26.10.4 for Linux.
| Product and line | Affected | Fixed build | Bulletin |
|---|---|---|---|
| NetScaler ADC and Gateway 14.1 | Before 14.1-73.57 | 14.1-73.57 | CTX697305 |
| NetScaler ADC and Gateway 13.1 | Before 13.1-64.39 | 13.1-64.39 | CTX697305 |
| NetScaler ADC 14.1-FIPS | Before 14.1-73.58 FIPS | 14.1-73.58 FIPS | CTX697305 |
| NetScaler ADC 13.1-FIPS and 13.1-NDcPP | Before 13.1-37.293 | 13.1-37.293 | CTX697305 |
| NetScaler Console 14.1 | Before 14.1-74.34 | 14.1-74.34 | CTX697320 |
| Secure Access Client for Windows | Before 26.11.1.6 | 26.11.1.6 | CTX697280 |
| Secure Access Client for Linux | Before 26.10.4 | 26.10.4 | CTX697281 |
Citrix only lists supported lines. Nothing older than 13.1, such as 13.0 or 12.1, appears in the bulletin, so there's no fixed build for it. If one of those is still running, the only way out is an upgrade to 14.1 or 13.1.
13.1 is living on borrowed time. Citrix's release-cycle article says it's already past end of maintenance, and its end of life is due next year (the dates are in the timeline below). It got a fix this time. If you're opening a change window anyway, we'd look hard at moving to 14.1 instead, since that's the line Citrix will support longest.
NetScaler in 2026, and what's next
- Mar 30, 2026First NetScaler flaw of the year on KEV
CVE-2026-3055, an out-of-bounds read, goes on CISA's exploited list. US federal agencies get a deadline to fix it. For everyone else it's a warning to patch.
- Apr 15, 2026NetScaler Console 13.1 reaches end of life
Citrix brought this date forward from 2027. On-premises Console now needs 14.1 to get fixes.
- Aug to Oct 2026Five more NetScaler flaws on KEV
CISA adds CVE-2026-8452, CVE-2026-19490, CVE-2026-88771, CVE-2026-88772 and CVE-2026-88779. That's five in under six weeks.
- Sep 15, 2026ADC 13.1 enters end of maintenance
13.1 leaves its maintenance phase. It still got a fix in November, but Citrix doesn't promise one every time.
- Nov 12, 2026Four bulletins published
28 ADC and Gateway flaws, the Console bypass and two Secure Access Client fixes. The clock starts for everyone running NetScaler themselves.
- Sep 15, 2027ADC 13.1 end of life
After this, 13.1 gets no more fixes. Plan the move to 14.1 before then.
- Gateway on a 14.1 or 13.1 build older than the November fix
- NSIP and Console open to the internet, so anyone who scans can find them
- Console still on 13.1, past end of life
- HA pair left on mismatched builds after a rushed upgrade
- Laptops on an old Secure Access Client
- Every appliance on 14.1-73.57, 13.1-64.39 or the matching FIPS build
- NSIP and Console reachable only from a management network
- Console on 14.1-74.34
- Both HA nodes on the same build, sync working again
- Laptops get the new VPN client from the endpoint tool, so nobody waits on users
What to do now
Start with an inventory, because NetScaler has a way of turning up in more places than people remember. The Gateway is easy to find. Pairs of VPX instances load balancing an internal app, an old SDX in a branch, the Console VM: those get forgotten. For each one, write down the build, whether it's an HA pairdefinitionTwo NetScaler appliances set up so one takes over if the other fails. Both must run the same build, which is why the upgrade order matters. and whether its management address can be reached from outside.
What to do now, by who you are
- Ask IT or your managed provider whether you run NetScaler yourselves or on Citrix's cloud, and get the list of appliances in writing.
- Approve a short outage window this week. Upgrading an HA pair means a failover, and remote users may drop once.
- If anything is older than 13.1, approve the upgrade project now. Those builds won't get a fix.
- Upgrade ADC and Gateway to 14.1-73.57 or 13.1-64.39. FIPS and NDcPP boxes take 14.1-73.58 FIPS or 13.1-37.293 instead.
- On HA pairs, upgrade the secondary first, fail over, then upgrade the other node. Don't leave them on different builds.
- Check that the NSIP only answers on a management network, and add ACLs if it doesn't.
- Upgrade NetScaler Console to 14.1-74.34 and keep its IP off any network strangers can reach.
- List the sign-in methods on each Gateway and AAA virtual server: SAML, LDAP, Email OTP, KBA, client certificates, EPA.
- After the upgrade, test a sign-in through each method with the identity provider behind it, such as Entra ID or Okta.
- Treat anything written to /var/log/httperror.log as exposed to whoever can read it, and limit shell access to the appliance.
- Push Secure Access Client 26.11.1.6 to Windows laptops and 26.10.4 to Linux ones. Until they update, a standard user on that laptop can make themselves SYSTEM or root.
- Pull a report from your endpoint tool of laptops still on older clients, and chase the ones that don't update.
# Which build is this box on, and is it the HA secondary? > show ha node Master State Secondary # Secondary, with sync off. That's the node you upgrade first, then fail over # On a saved copy of ns.conf: patterns from Citrix's bulletin $ grep -E "add (vpn|authentication) vserver" ns.conf add vpn vserver gw_remote SSL 203.0.113.10 443 # Got a match? Then the Gateway flaws, CVE-2026-107412 among them, apply to this box
Citrix's bulletin lists the configuration lines that make each flaw apply, which saves a lot of guessing. Use it to decide the order, and don't use it as a reason to skip the upgrade. CVE-2026-120868 needs no feature at all, so every box gets the new build in the end.
Harden so the next one hurts less
Citrix has put out several NetScaler bulletins this year, and six of the bugs ended up on CISA's exploited list. The teams that cope are the ones who can upgrade a pair on short notice and whose management side is already out of reach.
Durable fixes, tied to this case
- 01Keep the NSIP and Console off the internet
Citrix's secure deployment guide says the NSIP shouldn't be exposed to the public internet and should sit behind a stateful firewall. Management access on the NSIP can't be switched off, so filter it with ACLs. That shrinks the list of people who can try CVE-2026-120863 or the Console bypass.
- 02Separate management traffic from user traffic
Recent NetScaler releases include Secure Management, which gives the management plane its own routing table. Make sure that plane has a route back to your management network before you reboot, or you'll lock yourself out.
- 03Use HTTPS only for the admin GUI
Replace the default certificate, then run set ns ip <NSIP> -gui SECUREONLY so the admin page never answers over plain HTTP. It's a small change, and Citrix lists it among its key recommendations.
- 04Rehearse the HA upgrade before you need it
Citrix's HA procedure upgrades the secondary first and warns that config sync, command propagation and connection mirroring can stop while the two nodes are on different builds. Write the runbook down and time it once. Then a critical bulletin is routine work instead of a scramble.
- 05Put an end date on every NetScaler line
13.1 reaches end of life on September 15, 2027, and Console 13.1 is already past it. Budget the move to 14.1 now, before a bulletin arrives that 13.1 doesn't get.
- 06Send NetScaler logs to your SIEM
Unexpected restarts, core dumps and new admin sessions are the first signs of someone testing these bugs. Alert on them so somebody looks at a crash the same day.
Before: anyone who finds the Gateway can try the NSIP and Console too
The Gateway answers the internet as it should, but the NSIP and the Console answer too, and the HA pair runs an old build.
After: strangers only ever see a patched Gateway
The Gateway runs 14.1-73.57, the NSIP and Console sit on a management network, and both HA nodes match.
If you think you've been breached
If someone may have used one of these flaws
Citrix hasn't published indicators of compromise for this batch. Look for things nobody planned: unexpected appliance restarts or core dumps, admin sessions from addresses you don't know, files or config changes on the box, and new outbound connections from the NSIP.
- 01Containfirst hour
- Block outside access to the NSIP and Console. Keep the Gateway running if you can, since staff depend on it.
- Save logs, core files and a copy of the running configuration before you upgrade or reboot anything.
- Call your lawyer and cyber insurer early. Notice clocks often start from the first suspicion.
- 02Investigatefirst day
- Read the appliance logs for crashes and restarts since November 12, and around the time anyone first saw the box misbehave.
- Compare the running configuration with your last known-good backup, line by line.
- Check NetScaler Console audit logs for logins and changes nobody remembers making.
- 03Removefirst days
- Ask Citrix support whether you can upgrade in place or should rebuild from a clean image.
- If you rebuild, restore the configuration from a backup taken before November 12 and review it first.
- 04Recoverthis week
- Rotate what the box holds: nsroot and other admin passwords, LDAP bind accounts, RADIUS secrets, SAML signing keys and TLS private keys.
- End all active Gateway sessions so stolen session tokens stop working, and make users sign in again.
- If Console was touched, rotate the credentials it stores for each managed NetScaler.
- 05Report and learnthis month
- Work out with your lawyer who needs telling, based on what the logs show.
- Find out how the NSIP or Console became reachable and fix the change process behind it.
What this could look like
Three typical setups
- the setup
- A law firm's staff reach their virtual desktops through a NetScaler Gateway HA pair on a 14.1 build from the summer. The provider patches when a ticket comes in.
- what happens
- The default-config bug and the Gateway and ICA proxy flaws all apply. Nobody has opened a ticket yet.
- what to do
- Open the ticket today and ask for 14.1-73.57 on both nodes this week, the secondary first. Ask the provider to confirm in writing that the NSIP isn't public.
- the setup
- The Gateway signs users in through a SAML action pointing at Microsoft Entra ID, with Email OTP as a fallback. The Console VM is still on 13.1.
- what happens
- The SAML and Email OTP flaws apply on top of the default-config one. Console 13.1 isn't on the fixed list at all, because it's past end of life.
- what to do
- Upgrade the Gateway this week and test SAML and Email OTP sign-in afterwards. Build a Console 14.1-74.34 instance and retire the 13.1 VM.
- the setup
- An operator load balances SMPP for text messaging and runs DNS recursion on a pair of ADC appliances on 13.1. There's no Gateway.
- what happens
- The SMPP and DNS flaws apply, plus the default-config bug. 13.1 still gets a fix, but it's past end of maintenance.
- what to do
- Install 13.1-64.39 now. Then plan the move to 14.1 before 13.1 reaches end of life in September 2027.
How Cohash helps
Whoever runs NetScaler for you, in-house or a provider, does the upgrade. We pick up the work around it. Our network security people move management addresses off the internet and write the ACLs. Our identity and access team tests every sign-in path after the upgrade, whether the Gateway trusts Microsoft Entra ID or Okta. If you need hands for a run of upgrades, an Entra engineer can work next to your team. A free assessment is a good start if you're not sure what's exposed.
What to take from this
- 01
Citrix fixed 28 NetScaler ADC and Gateway flaws on November 12. One affects every appliance, even with the default configuration.
- 02
Install 14.1-73.57 or 13.1-64.39, or the matching FIPS build. On HA pairs, do the secondary first.
- 03
Upgrade NetScaler Console to 14.1-74.34 and keep it away from untrusted networks. Console 13.1 gets no fix.
- 04
Gateways that sign people in with SAML, LDAP, Email OTP or EPA have extra flaws. Test each sign-in method after the upgrade.
- 05
None are known exploited yet, but six NetScaler flaws made CISA's list this year. Don't wait for the seventh.
01Is anyone exploiting the November NetScaler flaws yet?
Citrix's bulletins don't say so, and none of them were on CISA's Known Exploited Vulnerabilities list in the catalog CISA released on November 13. That could change fast. Six NetScaler flaws were added to that list earlier in 2026.
02We use Citrix's cloud service. Do we need to do anything?
For the ADC and Gateway flaws, mostly no. Citrix says it upgrades the Citrix-managed cloud services and Citrix-managed Adaptive Authentication itself. If you run Secure Private Access in a hybrid setup, though, the NetScaler instances in it are yours to upgrade.
03Which NetScaler build fixes these flaws?
14.1-73.57 or later for 14.1, and 13.1-64.39 or later for 13.1. FIPS appliances need 14.1-73.58 FIPS, or 13.1-37.293 for 13.1-FIPS and 13.1-NDcPP. NetScaler Console needs 14.1-74.34.
04Is my NetScaler affected if I only use it as a load balancer?
Yes. CVE-2026-120868 hits every NetScaler ADC and Gateway, even one left on defaults. If untrusted hosts can reach the NSIP, the management-plane flaw applies too. The rest depend on what you've set up, and a few sign-in ones, like SAML or Email OTP actions, count on a plain ADC as well. Citrix's bulletin gives the config line to look for with each.
05We still run NetScaler Console 13.1. Is there a fix?
No. Citrix moved Console 13.1's end of life forward to April 15, 2026, and the bulletin only lists 14.1 as fixed. You'll need to move to Console 14.1-74.34.
06How do I upgrade a NetScaler HA pair without a long outage?
Citrix's procedure upgrades the secondary node first, then fails over and upgrades the other one. Config sync and connection mirroring can stop while the two are on different builds, so finish both nodes in the same window.
07Does NetScaler 13.0 get a fix?
It isn't on Citrix's list. Citrix only lists supported lines as affected and fixed, which for ADC and Gateway means 14.1 and 13.1. Anything older needs an upgrade to one of those.
Three questions, about a minute
Pick an answer and we'll tell you if it's right, and why it is or isn't. The score stays in this browser.
-
Q1Your NetScaler only load balances a web app, with no Gateway or sign-in features. Do the November fixes matter?
show the answer
B. Yes. CVE-2026-120868 hits every box, even one still on defaults Citrix's own precondition for CVE-2026-120868 is the default configuration, with nothing extra switched on. So a plain load balancer is exposed too, and it needs the new build like any Gateway.
-
Q2You're upgrading a NetScaler HA pair. Which node goes first?
show the answer
C. The secondary, then fail over and do the other one Citrix's HA procedure starts with the secondary. While the builds differ, config sync and connection mirroring can be off, so finish both nodes in one window.
-
Q3An admin wants the Console fix for a NetScaler Console 13.1 VM. What's the right answer?
show the answer
B. There's no 13.1 fix. Move to Console 14.1-74.34 Console 13.1 reached end of life on April 15, 2026, and the bulletin lists only 14.1-74.34 as fixed. 13.1-64.39 is the ADC and Gateway build, which is a different product.