Safeguard
Vulnerability Analysis•

CVE-2026-88779: High Memory Overflow in Citrix NetScaler

CVE-2026-88779 is a high memory overflow flaw in Citrix NetScaler (7.5). Check your version, apply the fix and limit access until you have. Steps inside.

Safeguard Security Team
3 min read

CVE-2026-88779 is a high severity memory overflow flaw in Citrix NetScaler, scored 7.5. Upgrade to the first build past each boundary listed below. Check your installed version against the affected list below, then patch or restrict access until you can. CISA lists it as exploited, so move quickly.

What's affected

  • NetScaler ADC before 14.1-73.41, before 13.1-64.28, before 14.1-73.41 FIPS, and before 13.1-37.282.
  • NetScaler Gateway before 14.1-73.41 and before 13.1-64.28.

Severity in the record: High (7.5), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Weakness: CWE-119.

Fix: Upgrade to the first build past each boundary listed below.

How to check if you're exposed

  1. Read the build from the appliance CLI: show ns version.
  2. Compare it with the boundaries above for your release line.

Run these on every affected device, including ones in remote sites, labs and spares that are powered on.

What to do now

  1. Confirm the version of every affected system using the checks above.
  2. Read the vendor advisory linked in Sources and note the fixed version for your release line.
  3. Schedule the update, starting with systems that face untrusted networks or hold the most sensitive data.
  4. In the meantime: read the Citrix TechZone blog on this CVE for guidance.
  5. Record the change, then recheck the version to confirm it took effect.

Why it matters

The record classes this as CWE-119 and rates it 7.5 with no privileges needed and high availability impact, a denial of service. It is in CISA's Known Exploited Vulnerabilities catalog. These builds are newer than those in the September bulletin, so a device patched then may still need this update.

CISA's Known Exploited Vulnerabilities catalog lists this CVE, which means exploitation has been observed. Federal agencies have remediation deadlines for KEV entries, and every other organization should treat the listing as a signal to patch first.

Network and management devices are patched less often than servers, because upgrades mean planned downtime. That gap is where a flaw like this stays open longest, so build the version check into your regular inventory.

The vector string in the record is a compact summary of how the flaw is reached and what it costs. AV is the attack vector (network, adjacent or local), PR is the privilege the attacker needs, and the C, I and A letters give the impact on confidentiality, integrity and availability. Read it against your own network layout rather than relying on the score alone.

After you patch

Patching is not the end of the job. Recheck the version on each system, because an upgrade that failed or rolled back looks the same as a success until someone looks. Keep the advisory link with your change record so the next reviewer can see why the update happened.

If you cannot patch soon, write down the reason, the compensating control you chose and a date to revisit. Exceptions without a date tend to become permanent.

Quick check

I patched in September. Am I covered?

Not necessarily. This CVE needs 14.1-73.41 or 13.1-64.28 (or the other builds above).

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.