Hacks & Data Breaches ThatGuy[A] · изменено

Citrix NetScaler zero-days exploited in the wild

This one is for the people who keep edge infrastructure alive — and a good, honest case study in how “exploited in the wild” is actually established. On 27 September 2026 Citrix published a security bulletin covering eight new vulnerabilities in NetScaler ADC and NetScaler Gateway (CVE-2026-88771 through CVE-2026-88778), and the same day CISA added two of them to its Known Exploited Vulnerabilities catalog and issued an amplifying alert the same day. Everything below comes from those primary sources — the Citrix bulletin, the CISA alert and CISA’s own KEV feed — read today, 29 September 2026. Where the sources don’t say something, neither will we.

What is confirmed. Two of the eight are critical zero-days that can each independently lead to remote code execution, and both have been seen exploited on unmitigated deployments. CVE-2026-88771 is unauthenticated RCE through improper input validation — Citrix’s table says it affects every NetScaler ADC and NetScaler Gateway deployment, including default configuration, with no additional features required (CVSS v4.0, 9.5). CVE-2026-88772 is a memory overflow that can give RCE or denial of service, and its precondition is DTLS being enabled — which, per the bulletin, is the default on VPN virtual servers (CVSS v4.0, 9.5). CISA states it has received reports and partner threat intelligence confirming that threat actors are actively exploiting these two globally. On the scale of evidence that is a high bar: vendor observation plus a government KEV entry, not a rumour with a screenshot.

The other six are not nothing: HTTP request smuggling (CVE-2026-88773, 9.3), a WAF and security-rule bypass through URL normalization (CVE-2026-88774, 7.0 — the bulletin notes this one was already addressed in all builds since 14.1-72.x and was reported externally), three more memory overflows with configuration preconditions (CVE-2026-88775 through CVE-2026-88777, 8.8 each), and TCP initial sequence number prediction (CVE-2026-88778, 8.8). Citrix’s bottom line is blunt: every NetScaler ADC and NetScaler Gateway is affected by at least one of the eight.

Fixed versions, straight from the bulletin: NetScaler ADC and NetScaler Gateway 14.1-73.37 or later in that branch; 13.1-64.23 or later in the 13.1 branch (with a caveat below); NetScaler ADC 14.1-FIPS 14.1-73.37 FIPS or later; NetScaler ADC 13.1-FIPS and 13.1-NDcPP 13.1.37.279 or later. The bulletin asks customers to check each CVE’s preconditions against their own configuration — virtual server types, DTLS, ORACLE load balancing vserver, non-HTTP L7 protocol features and so on — and prioritise the deployments where those conditions actually match.

Patch order matters here, and both sources are explicit about it. CISA urges checking for indications of compromise before patching if you can, and preserving forensic evidence before applying updates, because the update can take that forensic visibility with it. Citrix publishes indicators of compromise through NetScaler Console and has a separate document on steps to take if a NetScaler ADC is suspected compromised. The practical version: if you think you were hit, collect evidence first, then patch; if you are confident you were not, patch first and hunt afterwards. Citrix also recommends forwarding NetScaler logs to an external logging or SIEM platform and using NetScaler Console File Integrity Monitoring. Two operational caveats from the bulletin worth reading before you touch production: if the command `show ns variable` returns configured variables, the bulletin says to go to 13.1-64.24 instead of 13.1-64.23 to avoid an operational issue; and NetScaler Console’s CVE scan may incorrectly flag 13.1-64.23 as vulnerable until an advisory update is pushed, which needs no action from you.

For the US federal side: CISA’s KEV feed gives both entries a remediation due date of 30 September 2026 under Binding Operational Directive 26-04, and marks their known ransomware campaign use as “Unknown” — an honest blank rather than a denial.

What is not confirmed, and we are not going to pretend otherwise: who is exploiting these, how many organizations are affected, whether any particular sector is being targeted, or what the attackers do after getting in. The primary sources say none of that. If you run into a post that does, ask it for its primary source.

What this means for you. If you administer NetScaler, this is drop-everything territory: the CVE-2026-88771 precondition is effectively “you turned it on”, the fixes are published, and exploitation is confirmed by both the vendor and CISA. If you do not run this class of gear, treat the story as a template for reading vulnerability news at all: vendor bulletin first, KEV and exploitation status second, third-party write-ups last — and notice how much calmer the story becomes when you only carry the confirmed parts. That is also the editorial standard for this community: confirmed breaches and confirmed exploitation here, policy and platform freedom discussions in Digital Rights & Policy, and Android installation rules in Android & App Freedom.

Questions for the room: for those running edge appliances, what decides your order of operations — patch immediately, or collect forensics first? Do KEV deadlines actually drive your patch queue, or is it internal risk scoring that wins? And what would you want in a “confirmed exploited” standard before you personally believe a claim?

Sources (all checked 29 September 2026):
- Citrix security bulletin CTX697096 (authoritative statement; community copy last updated 27 September 2026): https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX697096
- Citrix bulletin community copy: https://community.citrix.com/techzone-blogs/110_security-updates/netscaler-adc-and-netscaler-gateway-security-bulletin-for-cve-2026-88771-through-cve-2026-88778/
- CISA alert, released 27 September 2026: https://www.cisa.gov/news-events/alerts/2026/09/27/critical-zero-day-vulnerabilities-exploited-citrix-netscaler-adc-gateway
- CISA KEV addition, 27 September 2026: https://www.cisa.gov/news-events/alerts/2026/09/27/cisa-adds-two-known-exploited-vulnerabilities-catalog
- CISA KEV catalog (entries added 2026-09-27, due 2026-09-30): https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Citrix: steps to take if NetScaler ADC is suspected to be compromised: https://support.citrix.com/external/article/CTX694799/steps-to-take-if-netscaler-adc-is-suspec.html

↑ 5

Обсуждение

Комментарии

1

На каждом уровне сначала новые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

For me it's decided by exposure rather than deadline: if the box is internet-facing and CVE-2026-88771 really bites at default config, it's patch first and hunt after, because the window is already open and the logs are only useful if they still exist. KEV is a useful tiebreaker when I'm arguing with someone about maintenance windows, but my own scoring usually gets there first. On forensics: I'd only slow down if I already had a heartbeat on the box and something looked off.