Citrix NetScaler ADC/Gateway — heap overflow during SAML SignedInfo canonicalization; CVE record describes only Denial of Service, but watchTowr published a pre-authentication chain to root (identifier is watchTowr's inference). Fixed in 14.1-72.61 / 13.1-63.18

UPDATE — the NetScaler flaw this pipeline recorded as a denial-of-service issue is a pre-authentication root shell: watchTowr publishes the full SAML SignedInfo overflow chain, and the sibling CitrixBleed bug has been carried as actively exploited since July

UPDATE · originally covered CVE-2026-8451 — Citrix NetScaler ADC/Gateway: pre-auth SAML memory overread (CitrixBleed lineage), public PoC (2026-07-01)

the original entry covered Citrix's six-CVE NetScaler bulletin and its headline flaw CVE-2026-8451, a pre-authentication memory overread in the SAML /saml/login parser, and described the companion CVE-2026-8452 as a denial-of-service and undefined-control-flow memory-management issue in Gateway and AAA vserver configurations. That description was faithful to the vendor's CVE record and is now known to be a serious understatement. Two deltas follow, and the second is a correction to this pipeline's own record.

The bug published as a memory-overflow issue is a pre-authentication root shell. watchTowr identifies its target from the public record's own wording, writing that "we believe this is CVE-2026-8452 given its description as a “Memory Overflow” vulnerability" — the same sparse framing behind the denial-of-service characterisation this pipeline carried on 1 July from Citrix's bulletin. On 2026-08-14 watchTowr Labs published a chain that ends in a root command shell, entirely pre-authentication (watchTowr Labs, 2026-08-14). The identifier is an inference rather than a confirmation — watchTowr says so plainly, and Switzerland's NCSC describes the work as "A new technical analysis, likely related to CVE-2026-8452, was published by Watchtowr" (NCSC-CH, 2026-08-14) — but the bug watchTowr analysed is fixed by the same release, so the operational conclusion does not depend on resolving the mapping.

The kill chain. The defect is in SAML signature canonicalization: "During signature canonicalization, earlier versions of the NetScaler solution copy attacker-controlled data from the SAML message's ds:SignedInfo element into a fixed-size global buffer, without checking whether it actually fits" (watchTowr Labs, 2026-08-14). The attacker-controlled field is the PrefixList attribute of the InclusiveNamespaces element inside the ds:SignedInfo block, and the copy target sits in nsppe, NetScaler's packet-processing engine. An oversized value overflows linearly into the header of the adjacent chunk in the appliance's network-buffer pool, corrupting that neighbour's data-pointer and freelist-link fields. The corruption becomes an attacker primitive later, when the packet engine retrieves that chunk and performs a memcpy using the corrupted pointer as its destination with an attacker-influenced length: "So we now have a memcpy copying from our packet to any address we want, which is a write-what-where primitive." From there the exploit is unusually cheap, because the target offers almost no mitigations — "The nsppe binary lacks almost all of the protections you'd hope to find, and the heap is executable, for reasons known only to Citrix" — so watchTowr redirected execution into shellcode placed on a heap that is both executable and at a fixed address, and "nsppe already runs as root, so our shellcode executes as root too."

Two engineering details in the chain matter to defenders more than the memory corruption does. First, an nsppe crash normally triggers a full appliance reboot through a watchdog process, which would destroy anything the attacker dropped; watchTowr neutralised the packet engine's crash-signal handlers so the watchdog merely respawned the process instead of rebooting the box, letting a dropped PHP webshell survive. Second, because the web server executing that webshell runs as an unprivileged account while nsppe runs as root, the exploit set the SUID bit on /bin/sh from the root shellcode so that commands issued through the webshell execute with a root effective UID (watchTowr Labs, 2026-08-14). The result is durable root that survives the process restart an operator would most likely dismiss as a glitch.

Reachability. watchTowr states the vulnerability "is reachable when the Netscaler appliance is configured to use SAML as either a Service Provider (SP) or an Identity Provider (IdP)" (watchTowr Labs, 2026-08-14) — which, in the deployment terms Citrix's bulletin used and this pipeline recorded on 1 July, is any appliance acting as a Gateway or AAA virtual server. That is the ordinary shape of a remote-access appliance in a European government or critical-infrastructure network, and it is broader than the sibling flaw's precondition: NCSC-CH records that one as requiring the appliance to be configured as a SAML Identity Provider specifically (NCSC-CH, advisory of 2026-07-03). Affected are NetScaler ADC and Gateway 14.1 before 14.1-72.61 and 13.1 before 13.1-63.18, and both CVE records additionally list the FIPS and NDcPP builds — 14.1 FIPS before 14.1-72.61 and 13.1 FIPS/NDcPP before 13.1-37.272, a different fixed build that an estate running certified appliances has to check for separately. Both flaws were fixed together in that June/July release. No party reports in-the-wild exploitation of the code-execution chain.

The correction. The original entry recorded that no in-the-wild exploitation of CVE-2026-8451 was confirmed at disclosure. NCSC-CH's advisory on that flaw, timestamped 2026-07-03, states its current exploitation status as "Actively Exploited, Proof of Concept Available", and cites reporting that it was exploited immediately after public disclosure (NCSC-CH, advisory of 2026-07-03, updated 2026-08-14). That status has stood since early July and this pipeline did not carry it — so an estate that read the 1 July entry and concluded the memory-overread flaw was unexploited was working from a stale picture for six weeks. The exploitation is not new; the record here was wrong.

Triage: the distinctive telemetry is a crash that does not behave like a NetScaler crash. In appliance system and error logs, an nsppe process restart without the full appliance reboot that normally follows one is the signature this exploit deliberately produces, and it is worth correlating against inbound SAML authentication attempts in the same interval. On the request side, SAML AuthnRequest and Response bodies carrying an anomalously large InclusiveNamespaces PrefixList attribute inside a SignedInfo block are the delivery shape — legitimate SAML messages carry short namespace-prefix lists, so length is a usable discriminator here rather than a heuristic. Where any host-level telemetry is available from the appliance, a shell process spawned by the web server is decisive: a NetScaler web server has no legitimate reason to spawn a shell, and the SUID step means the shell will carry a root effective UID under a process that should never have one.