CVE-2026-8452: The NetScaler Gateway Memory Overflow. Are You Actually Exposed?
On August 26, 2026, CISA added CVE-2026-8452 to its Known Exploited Vulnerabilities catalog with a remediation due date of August 29 — a three-day federal clock that has already passed. It affects Citrix NetScaler ADC and NetScaler Gateway, the same appliance family behind a string of the worst edge-device incidents of the last few years. But the useful detail in this one is a precondition: it only applies if the box is doing a specific job. If yours is, this is a today problem; if it isn't, you can move it down the list with confidence instead of panic.
One thing to get straight up front, because the NetScaler name invites the wrong assumption: this is not another CitrixBleed-style memory-disclosure or a remote code execution bug. Per the NVD record, CVE-2026-8452 is a memory-overflow flaw that leads to "unpredictable or erroneous behavior and Denial of Service." The observed, described impact is the appliance falling over — not credential theft and not attacker code running on the box. That distinction matters for how you prioritize it, and it's the kind of thing that gets lost when a headline just says "critical NetScaler bug."
What CVE-2026-8452 actually is
NVD describes it as a "Memory overflow vulnerability" in NetScaler ADC and NetScaler Gateway "leading to unpredictable or erroneous behavior and Denial of Service if the appliance is configured as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server." It is classified as CWE-119, a memory-buffer bounds error.
The scoring is worth reading honestly. NVD carries two CVSS vectors for it: a CVSS 3.1 base of 9.8 (Critical) and a CVSS 4.0 base of 8.8 (High). The gap is normal for a denial-of-service flaw — 3.1 tends to rate network-reachable, unauthenticated bugs at the top of the scale, while 4.0's vector reflects that the primary impact here is availability rather than a full confidentiality-and-integrity compromise. Either way it is remotely reachable and needs no authentication, which is exactly why it landed in KEV.
The precondition is the whole story
A NetScaler is a versatile box. Plenty of them sit inside a data center doing nothing but load balancing and TLS offload for internal apps — never terminating a user VPN, never internet-facing. Per the advisory, those deployments are not in the exploitable configuration for this CVE. The vulnerable code path is reached only when the appliance is acting as a Gateway — SSL VPN, ICA Proxy, CVPN, or RDP Proxy — or as an AAA virtual server.
That is a genuinely actionable filter, and it is the first thing to check. If your NetScaler publishes a remote-access portal or brokers Citrix/RDP sessions to the internet, you are in scope and the clock already ran out. If it is a pure ADC doing internal load balancing, you should still patch on your normal cadence, but you are not sitting on an exposed, actively-exploited service. Knowing which of those two you are is the difference between a fire drill and a maintenance ticket.
Affected and fixed versions
Per NVD's configuration data, the affected supported branches and their fixed builds are:
- → 13.1 — affected before 13.1-63.18.
- → 14.1 — affected before 14.1-72.61.
- → 13.1-FIPS / NDcPP — affected before 13.1-37.272.
Citrix tracks FIPS and NDcPP editions on their own build lines, so confirm the exact fixed build for your edition against Citrix's advisory, CTX696604, before you schedule the upgrade. If you are on a branch older than 13.1, it is past end of maintenance — there is no fixed build coming, and the answer is to move to a supported branch rather than to wait for a hotfix.
What to do right now
- → Identify the role first. Determine whether each NetScaler runs a Gateway vserver (SSL VPN / ICA / CVPN / RDP Proxy) or an AAA vserver. That single fact tells you whether the box is exposed to this CVE.
- → Upgrade to a fixed build for exposed appliances — 13.1-63.18, 14.1-72.61, or the matching FIPS/NDcPP build. CISA's required action ties remediation to BOD 26-04 timelines and, where no fix is available, to discontinuing use.
- → Reduce exposure while you schedule the upgrade. A Gateway or AAA vserver that does not need to face the whole internet should be restricted at the perimeter. Reachability is the precondition for a remote DoS; narrowing who can reach the service narrows who can trip it.
- → Read CTX696604 for the authoritative per-edition build matrix and any Citrix-issued mitigations. Vendor advisory beats any third-party summary, including this one.
Where a config audit fits — and where it doesn't
Being straight about this: CRWLR does not audit Citrix NetScaler. It parses FortiGate, Palo Alto, Sophos, Check Point, and Cisco ASA configurations — not NetScaler — so it cannot tell you whether a specific appliance runs a vulnerable Gateway build. For NetScaler, the authoritative check is Citrix's advisory against your running version. No firewall config audit — ours or anyone's — can see inside a NetScaler, prove a binary was patched, or confirm a box hasn't already been knocked over. Those are the honest limits.
What does carry over is the pattern. CVE-2026-8452 is one more entry in the same story every quarter tells: the internet-facing remote-access gateway is the target, and an exposed VPN or portal service is where the perimeter turns into an entry point. On the firewalls CRWLR does parse, that is exactly the posture it reads — flagging SSL-VPN exposure, remote-access authentication that lacks MFA, deprecated VPN crypto, and firmware versions that match CISA KEV or NVD entries. Different vendor, same question: which of your edge devices are publishing a remote-access service you'd forgotten was internet-facing?
Know your firewall's VPN exposure before the next KEV entry lands
CRWLR audits FortiGate, Palo Alto, Sophos, Check Point, and Cisco ASA configs for SSL-VPN exposure, weak remote-access auth, and firmware CVE matches in about 60 seconds — no agents, no deployment. (NetScaler isn't supported; check CTX696604 for that one.)
Start Free Scan →60 seconds. No credit card. Raw configs never stored.
FAQ
What is CVE-2026-8452?
CVE-2026-8452 is a memory-overflow (CWE-119) vulnerability in Citrix NetScaler ADC and NetScaler Gateway. Per NVD, it leads to "unpredictable or erroneous behavior and Denial of Service" when the appliance is configured as a Gateway (SSL VPN, ICA Proxy, CVPN, or RDP Proxy) or as an AAA virtual server. NVD lists a CVSS 3.1 base score of 9.8 (Critical) and a CVSS 4.0 base score of 8.8 (High). CISA added it to the Known Exploited Vulnerabilities catalog on August 26, 2026, with a due date of August 29, 2026.
Is CVE-2026-8452 remote code execution or another CitrixBleed?
No. Based on the CISA KEV and NVD descriptions, the impact is denial of service — the appliance behaving unpredictably or crashing — not remote code execution and not the memory-disclosure/session-theft behavior of CitrixBleed (CVE-2023-4966). It should still be treated as urgent because it is on KEV and remotely exploitable without authentication, but the risk it describes is availability, not data theft.
Am I affected if my NetScaler only does load balancing?
Per the advisory, the vulnerable path is reached only when the appliance runs as a Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual server. A NetScaler doing only ADC load balancing and TLS offload, with no Gateway or AAA vserver configured, is not in the exploitable configuration for CVE-2026-8452. Patch it on your normal cadence, but it is not the same emergency as an exposed remote-access gateway.
Which NetScaler versions are affected, and what are the fixes?
Per NVD's configuration data: the 13.1 branch is affected before build 13.1-63.18, the 14.1 branch before 14.1-72.61, and the 13.1-FIPS/NDcPP line before 13.1-37.272. Branches older than 13.1 are past end of maintenance and should be moved to a supported branch. Confirm the exact fixed build for your edition in Citrix's advisory CTX696604 before upgrading.
Is CVE-2026-8452 being exploited in the wild?
Its presence in the CISA KEV catalog (added August 26, 2026) means CISA has evidence of active exploitation; that is the bar for KEV inclusion. The KEV entry currently lists known ransomware-campaign use as "Unknown." Regardless of the ransomware status, a KEV listing means it should be treated as an urgent, patch-now item rather than triaged by internal severity scoring alone.
Does CRWLR scan Citrix NetScaler for this?
No. CRWLR parses FortiGate, Palo Alto, Sophos, Check Point, and Cisco ASA configurations, not Citrix NetScaler, so it cannot check a NetScaler for CVE-2026-8452. For NetScaler, use Citrix's advisory CTX696604 against your running build. CRWLR is useful for the analogous exposure on the firewall vendors it does support — SSL-VPN exposure, remote-access auth, and firmware CVE matches.
Keep reading
Two Cisco Secure Firewall flaws in KEV: one reloads your ASA, one hands out a login — the same edge-device pattern on a vendor CRWLR does parse, with the config lines that decide whether you're exposed.
Audit your firewall — pick your vendor
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.09.01); NVD record for CVE-2026-8452; Citrix advisory CTX696604. Facts current as of September 2, 2026.