CVE-2026-88771: Citrix NetScaler Flaw Under Active Exploitation, CISA Says

Evidence of real-world attacks puts CVE-2026-88771 on CISA's KEV list, with a remediation deadline of September 30, 2026.

Threat Times Exposure DeskSeptember 28, 20261 min read

Share LinkedIn Reddit

Illustration: A sleek black network appliance sits on a metal shelf with blank front panels and small indicator lights. — AI-generated illustration: Threat Times

Key points

CVE-2026-88771 affects Citrix NetScaler and is exploited in the wild.
CISA added it to the KEV catalog on September 27, 2026.
Federal agencies must remediate by September 30, 2026.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on September 27, 2026 added CVE-2026-88771, a memory corruption flaw in Citrix NetScaler, to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence that attackers are already using it.

At a glance

CVE: CVE-2026-88771
Vendor: Citrix
Product: NetScaler
CVSS: 9.5 CRITICAL
Weakness: memory corruption
Exploited: Yes (CISA KEV)
Ransomware use: Unknown
Patch deadline (FCEB): September 30, 2026

What is the vulnerability?

CISA's catalog entry describes the issue as follows: Citrix NetScaler ADC and NetScaler Gateway contain an improper input validation vulnerability that could allow an unauthenticated attacker to execute arbitrary commands.

The National Vulnerability Database lists a CVSS base score of 9.5 (Critical), vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

The NVD record adds: Improper input validation vulnerability in Citrix NetScaler ADC and Citrix NetScaler Gateway. This issue affects ADC: before 14.1-73.37, before 13.1-64.23, before 14.1-73.37 FIPS, and before 13.1.37.279 FIPS and NDcPP; Gateway: before 14.1-73.37 and before 13.1-64.23 leading to an unauthenticated attacker to execute arbitrary commands.

Why this matters

CISA does not currently link this vulnerability to ransomware campaigns, but KEV listings mean exploitation has already been observed. Under Binding Operational Directive 22-01, Federal Civilian Executive Branch agencies must remediate it by September 30, 2026. CISA urges every organisation, not only federal agencies, to treat KEV entries as a patching priority.

What should you do?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Apply the vendor's fix or mitigation now; CISA lists the bug as exploited in real attacks.
If no patch is available, follow the vendor's workaround or take the product offline.
Check logs on exposed systems for signs of compromise before and after patching.
Restrict management interfaces so they are not reachable from the internet.

What to do and how to stay safe: CVE-2026-88771

Patch scores alone ignore context like network exposure and asset criticality.
You must map vulnerabilities to specific business risks to prioritize correctly.
Continuous exposure data replaces static scanning for accurate prioritization.

Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.

Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.