// threat brief

CVE-2026-88779Actively exploited

NetScaler ADC and Gateway SAML memory overflow: attackers can crash the appliance without an account, exploited in the wild

CVSS
7.5 HIGH
CISA KEV
2026-10-04
Weakness
CWE-119

PlainCVE Team · Published 2026-10-12 · AI-assisted · Press brief ↓

AI review 2026-10-12 (not human-reviewed)Command tests: none yetReproduced: not yetVerification record ↓

A memory overflow in SAML-configured NetScaler ADC and Gateway lets attackers crash the appliance with no account. Exploited in the wild.

Who is affectedCustomer-managed NetScaler ADC and NetScaler Gateway: 14.1 before 14.1-73.41, 13.1 before 13.1-64.28, and the matching FIPS/NDcPP builds, when Citrix's preconditions are met. Citrix's blog post says the issue is associated with deployments that use SAML authentication in conjunction with Gateway or AAA functionality, and customers who deployed NetScaler as a Gateway or AAA virtual server should check the configuration for add authentication samlAction (configured as a SAML SP) or add authentication samlIdPProfile (configured as a SAML IdP); Citrix bulletin CTX697174 states the precondition as the appliance being configured as a SAML SP or IdP. Secure Private Access Hybrid deployments that use NetScaler instances are also affected.
What happensAn attacker can crash the appliance over the network. If this is triggered repeatedly, the service may stay down and legitimate users are cut off. As quoted by the press, Citrix says it has not found any impact on the integrity of customer data. Some reports suggest remote code execution may also be possible, but that is unconfirmed and researchers disagree.
What to do nowUpgrade as soon as possible to 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS or 13.1-37.282 or later. If you already upgraded for CVE-2026-88771 through 88778 and you meet the SAML conditions, you need to upgrade again.
Affected versionsADC and Gateway 14.1 before 14.1-73.41 and 13.1 before 13.1-64.28; ADC 14.1-FIPS before 14.1-73.41 FIPS (NVD's data also marks 14.1-73.41 itself as affected, which differs from Citrix); ADC 13.1-FIPS and 13.1-NDcPP before 13.1-37.282. Exploitable only when the preconditions are met; the Citrix bulletin says the appliance is configured as a SAML SP or IdP, and the Citrix blog says the issue is associated with SAML authentication used with Gateway or AAA functionality.
Fixed versions14.1-73.41 and later; 13.1-64.28 and later 13.1 releases; 14.1-73.41 FIPS and later 14.1-FIPS releases; 13.1-37.282 and later 13.1-FIPS and 13.1-NDcPP releases.
CVSS vector
Show full vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Timeline
  • First public 2026-10-03
CISA KEVListed (2026-10-04): attacks have been seen in the wild

Blue team playbook

Check, fix / mitigate, respond, harden. Matching the affected versions does not mean you were compromised, and a check that finds nothing does not prove you are safe; each item says what it can and cannot show. Tagged steps point to where the attack flow below can be stopped.

DETECTCheckAm I affected? Any signs of compromise?
  1. 01Check your version

    Run on the NetScaler CLI (read-only). Compare your version with the affected ranges: 14.1 before 14.1-73.41, 13.1 before 13.1-64.28, 14.1-FIPS before 14.1-73.41 FIPS, 13.1-FIPS/NDcPP before 13.1-37.282. The bulletin covers only customer-managed appliances; Citrix updates its own managed cloud services itself.

    Read-only check
    show ns version
  2. 02Check whether you meet the SAML precondition

    Official guidance (Citrix bulletin CTX697174): inspect the NetScaler configuration for add authentication samlAction (SAML SP) or add authentication samlIdPProfile (SAML IdP). The command here is a read-only NetScaler CLI command and only a rough filter; show ns runningConfig follows the ns-runningconfig page of the official NetScaler command reference (https://developer-docs.netscaler.com/en-us/adc-command-reference-int/current-release/ns/ns-runningconfig), and grep follows its utility/grep page (https://developer-docs.netscaler.com/en-us/adc-command-reference-int/current-release/utility/grep), which gives the syntax grep [-c] [-E] [-i] [-v] [-w] [-x] pattern and shows grep piped after another CLI command. Combining the two into this one line is PlainCVE's own wording. Still check the filtered output against those two entries.

    Read-only check
    show ns runningConfig | grep -i saml
  3. 03Run Citrix's indicator-of-compromise script

    According to watchTowr's FAQ (also quoted by Help Net Security), Citrix provides an indicator-of-compromise (IoC) script through NetScaler Console to check appliances for signs of compromise; the Citrix bulletin and blog posts we read do not mention this script. watchTowr says it may produce false positives, so review results carefully.

  4. 04Use the community SIGMA rule to spot probing and exploitation

    According to Help Net Security, a threat hunter has shared a SIGMA rule for identifying probing, scanning and exploitation attempts. It is not provided by Citrix.

MITIGATEFix / mitigatePatch; block it if you cannot patch yet
  1. 01Upgrade to a fixed version

    Citrix strongly urges affected customers to install the updated versions as soon as possible: 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS or 13.1-37.282 or later.

  2. 02Already upgraded for the previous batch? Upgrade again

    Per Citrix's blog post: appliances already upgraded with a release from the CVE-2026-88771 through CVE-2026-88778 bulletin must be upgraded again with the release from the CVE-2026-88779 bulletin if they meet the preconditions.

  3. 03Can't upgrade yet: Global Deny List signatures

    Per Citrix's blog post (Citrix bulletin CTX697174 itself lists no mitigation other than upgrading): Citrix released signatures that can be used through the Global Deny List feature. Prerequisites: you use NetScaler Console on-premises (with Cloud Connect) or NetScaler Console service, with the "Virtual patching" status set to "Enabled" in NetScaler Console settings; and your build is >= 14.1-73.37 and < 14.1-73.41, or >= 13.1-64.23 and < 13.1-64.28. On the NetScaler CLI, run show appfw signatures and confirm that the Encrypted Version under "Name: *Default Signatures" is at least v24; then run stat denylist global AAA_REQUEST, where a count greater than 0 means the rules are working. Until you have confirmed this, do not assume you are protected. Citrix says the signatures can only help reduce risk and still recommends upgrading as soon as possible. Separately, the blog's "Additional Guidance" lists defense-in-depth advice: block suspicious IP addresses with the NetScaler blocklist feature and, where appropriate, use firewall rules to block traffic from IP addresses identified as attack sources; this is a different measure from the Global Deny List signatures.

RESPONDRespondIf you find signs of compromise
  1. 01Correlate crashes with attack attempts

    PlainCVE's suggestion: look for repeated crashes or forced reboots and compare them with the IoC script and SIGMA rule results. BleepingComputer reports one administrator whose logs showed attempted exploitation and correlated crashes, but could not confirm that commands actually ran.

  2. 02Investigate signs of exploitation as an intrusion

    PlainCVE's suggestion: Kevin Beaumont reported a downloaded malware binary running on one of his patched honeypots (whether this CVE caused it is not established). If you find signs of exploitation, don't treat it as a simple outage; investigate it as a possible intrusion.

HARDENHardenPrevent the next one
  1. 01Keep an inventory of SAML-enabled appliances

    PlainCVE's suggestion: only SAML-configured appliances are exploitable this time, and already-patched appliances still needed another upgrade. Knowing in advance which appliances use SAML lets you judge exposure faster when the next bulletin comes out.

  2. 02Have Virtual patching ready

    PlainCVE's suggestion: per Citrix's blog post, Global Deny List signatures need NetScaler Console with Virtual patching set to Enabled, and you need to confirm the signature version with show appfw signatures (at least v24 this time) and that the rule is working with stat denylist global AAA_REQUEST. Deciding ahead of time whether to enable it can buy time before a patch is installed, but it does not replace upgrading.

Full remediation steps and notes
  1. Check your version and SAML setup first. On the NetScaler CLI, show ns version shows the version; show ns runningConfig | grep -i saml is a rough, read-only way to find SAML configuration (the combined line is PlainCVE’s wording; grep syntax and piping follow the official NetScaler command reference’s grep page). The exact entries to match are the ones Citrix bulletin CTX697174 and Citrix’s blog post list: add authentication samlAction and add authentication samlIdPProfile.
  2. Ordering caveat. Per Citrix’s blog post: if you already upgraded with a release from the CVE-2026-88771 through CVE-2026-88778 bulletin and your appliance meets the preconditions, you need to upgrade again with the release from the CVE-2026-88779 bulletin. (Separately, per BleepingComputer: before the fix, customer appliances running 14.1-73.37 (the latest build at the time) were being forced to reboot repeatedly.)
  3. Stopgap: Global Deny List signatures. Per Citrix’s blog post (Citrix bulletin CTX697174 itself lists only upgrading), Citrix released signatures that can be used through the Global Deny List feature. Prerequisites:
    • You use NetScaler Console on-premises (with Cloud Connect) or NetScaler Console service, and the “Virtual patching” status is “Enabled” in NetScaler Console settings.
    • Your build falls in one of these ranges:
BranchBuilds covered
14.1>= 14.1-73.37 and < 14.1-73.41
13.1>= 13.1-64.23 and < 13.1-64.28

Then, on the NetScaler CLI, run show appfw signatures (read-only) and confirm the Encrypted Version under “Name: *Default Signatures” is at least v24; then run stat denylist global AAA_REQUEST (read-only) and check the rule-evaluation counters and Last Hit Time. A value greater than 0 means the rules are working.

Citrix says the signatures can only help reduce risk and still recommends upgrading to a fixed version as soon as possible. Until you have confirmed all of the above, do not assume you are protected.

Separately, the blog’s “Additional Guidance” lists defense-in-depth advice: block suspicious IP addresses with the NetScaler blocklist feature and, where appropriate, use firewall rules to block traffic from IP addresses identified as attack sources. This is a different measure from the Global Deny List signatures and does not replace upgrading.

  1. The IoC script can give false positives. Per watchTowr’s FAQ (as quoted by Help Net Security), the indicator-of-compromise script Citrix provides through NetScaler Console may flag false positives, so a person needs to review the results; the Citrix bulletin and blog posts we read do not mention this script.

Attack flow

Read left to right: this is the order the attack happens in. A blue shield means the step can be stopped; the earlier, the better. Click an icon for details.

Read top to bottom: this is the order the attack happens in. A blue shield means the step can be stopped; the earlier, the better. Tap an icon for details.

NetScaler ADC and Gateway SAML memory overflow: attackers can crash the appliance without an account, exploited in the wild: 1. The attacker sends requests to the NetScaler appliance over the network → 2. Because SAML is configured, the appliance processes the request → 3. A memory overflow happens while handling it → 4. The appliance crashes and service goes downCVE-2026-88779 · NetScaler ADC and Gateway SAML memory overflow: attackers can crash theappliance without an account, exploited in the wildAttackerYour systemThe attacker sends requests to the NetScaler appliance over the network — No valid account and no user interaction are needed (the CVSS vector shows AV:N, PR:N, UI:N; "no account needed" is watchTowr's description). 1The attacker sendsrequests to theNetScalerappliance over th…Because SAML is configured, the appliance processes the request — Citrix's blog post says the issue is associated with deployments that use SAML authentication in conjunction with Gateway or AAA functionality; Citrix bulletin CTX697174 states the precondition as the appliance being configured as a SAML service provider (SP) or identity provider (IdP). 2Because SAML isconfigured, theapplianceprocesses th…A memory overflow happens while handling it — The code operates outside the bounds of a memory buffer (CWE-119). 3A memory overflowhappens whilehandling itThe appliance crashes and service goes down — If triggered repeatedly, the service may remain unavailable (Citrix's statement, quoted by the press). According to BleepingComputer, citing NetScaler administrators on Reddit, customer appliances on 14.1-73.37 were already being forced to reboot over and over before the fix. 4The appliancecrashes andservice goes downAttack pathCan be stopped herePlainCVE · plaincve.date/en/vulns/cve-2026-88779-netscaler-saml-memory-overflow-dos · CC BY 4.0
NetScaler ADC and Gateway SAML memory overflow: attackers can crash the appliance without an account, exploited in the wild: 1. The attacker sends requests to the NetScaler appliance over the network → 2. Because SAML is configured, the appliance processes the request → 3. A memory overflow happens while handling it → 4. The appliance crashes and service goes downCVE-2026-88779 · NetScaler ADC andGateway SAML memory overflow: attackerscan crash the appliance without anaccount, exploited in the wildThe attacker sends requests to the NetScaler appliance over the network — No valid account and no user interaction are needed (the CVSS vector shows AV:N, PR:N, UI:N; "no account needed" is watchTowr's description). 1AttackerThe attacker sends requests tothe NetScaler appliance overthe networkBecause SAML is configured, the appliance processes the request — Citrix's blog post says the issue is associated with deployments that use SAML authentication in conjunction with Gateway or AAA functionality; Citrix bulletin CTX697174 states the precondition as the appliance being configured as a SAML service provider (SP) or identity provider (IdP). 2Your systemBecause SAML is configured, theappliance processes the requestA memory overflow happens while handling it — The code operates outside the bounds of a memory buffer (CWE-119). 3Your systemA memory overflow happens whilehandling itThe appliance crashes and service goes down — If triggered repeatedly, the service may remain unavailable (Citrix's statement, quoted by the press). According to BleepingComputer, citing NetScaler administrators on Reddit, customer appliances on 14.1-73.37 were already being forced to reboot over and over before the fix. 4Your systemThe appliance crashes andservice goes downAttack pathCan be stopped herePlainCVE · CC BY 4.0plaincve.date/en/vulns/cve-2026-88779-netscaler-saml-memory-overflow-dos
Free to use in reporting and teaching under CC BY 4.0. Attribution is already on the image.
  1. Attacker

    The attacker sends requests to the NetScaler appliance over the network

    No valid account and no user interaction are needed (the CVSS vector shows AV:N, PR:N, UI:N; "no account needed" is watchTowr's description).

    Defense: If you can't upgrade yet, Citrix's blog post offers Global Deny List signatures as a mitigation. Prerequisites are NetScaler Console (on-premises with Cloud Connect, or NetScaler Console service) with Virtual patching status Enabled, and a build >= 14.1-73.37 and < 14.1-73.41 or >= 13.1-64.23 and < 13.1-64.28. Use show appfw signatures to confirm the signature version is at least v24, and stat denylist global AAA_REQUEST to confirm the rule is being hit. Citrix says this can only help reduce risk and still recommends upgrading as soon as possible (Citrix bulletin CTX697174 itself lists only upgrading).

  2. Your system

    Because SAML is configured, the appliance processes the request

    Citrix's blog post says the issue is associated with deployments that use SAML authentication in conjunction with Gateway or AAA functionality; Citrix bulletin CTX697174 states the precondition as the appliance being configured as a SAML service provider (SP) or identity provider (IdP).

    Defense: As Citrix's blog post and bulletin describe, check the configuration for add authentication samlAction (SP) or add authentication samlIdPProfile (IdP) to see whether you meet the precondition.

  3. Your system

    A memory overflow happens while handling it

    The code operates outside the bounds of a memory buffer (CWE-119).

    Defense: Upgrade to 14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS or 13.1-37.282 or later.

  4. Your system

    The appliance crashes and service goes down

    If triggered repeatedly, the service may remain unavailable (Citrix's statement, quoted by the press). According to BleepingComputer, citing NetScaler administrators on Reddit, customer appliances on 14.1-73.37 were already being forced to reboot over and over before the fix.

    Defense: Watch for unexpected crashes and reboots. According to watchTowr (as quoted by Help Net Security), Citrix provides an indicator-of-compromise script through NetScaler Console that can be used to check; the Citrix bulletin and blog posts we read do not mention this script.

Who is affected

NetScaler ADC and NetScaler Gateway are network appliances many companies put in front of their internal applications and remote access. Citrix’s bulletin covers only customer-managed appliances; Citrix updates its own managed cloud services itself.

Product / branchAffectedFixed
ADC and Gateway 14.1Before 14.1-73.4114.1-73.41 and later
ADC and Gateway 13.1Before 13.1-64.2813.1-64.28 and later 13.1 releases
ADC 14.1-FIPSBefore 14.1-73.41 FIPS (Citrix); NVD lists up to and including 14.1-73.4114.1-73.41 FIPS and later (Citrix)
ADC 13.1-FIPS and 13.1-NDcPPBefore 13.1-37.28213.1-37.282 and later
Secure Private Access Hybrid deployments using NetScaler instancesCitrix says also affectedDepends on the version of the NetScaler instances used (PlainCVE’s reading)

Precondition: Citrix’s blog post says the issue is associated with NetScaler deployments that use SAML authentication in conjunction with Gateway or AAA (authentication, authorization and accounting) functionality; customers who deployed NetScaler as a Gateway or AAA virtual server should check whether SAML authentication actions are configured. To decide, look in the configuration for either of these entries: add authentication samlAction (appliance configured as a SAML SP) or add authentication samlIdPProfile (appliance configured as a SAML IdP). Citrix bulletin CTX697174 states the precondition as the appliance being configured as a SAML SP or SAML IdP, with the same configuration entries to check.

The 14.1-FIPS versions don’t match: Citrix says builds “before 14.1-73.41 FIPS” are affected, meaning 14.1-73.41 FIPS itself is fixed. NVD’s CPE data, however, marks versions up to and including 14.1-73.41 as vulnerable. Going by Citrix’s bulletin, upgrading to 14.1-73.41 FIPS or later is enough, but keep an eye on whether NVD updates its data.

How it works

SAML is a single sign-on standard: the IdP confirms who you are, and the SP accepts that verdict and logs you in. A NetScaler configured for SAML handles SAML-related requests coming from the network.

Citrix describes this flaw as a “memory overflow leading to denial of service” and classifies it as CWE-119 (operations outside the bounds of a memory buffer). In plain terms, while handling certain input the code reads or writes past the memory it should use, and the appliance crashes. The sources we reviewed do not give technical details of the flaw.

  • No account needed: the CVSS vector shows a network attack with low complexity, no privileges and no user interaction (AV:N/AC:L/PR:N/UI:N); watchTowr also says an attacker can cut off legitimate users without a valid account.
  • Impact: per the press, quoting Citrix, if the condition is triggered repeatedly the service may remain unavailable; Citrix also says it has not found any impact on the integrity of customer data.
  • Code execution is disputed: BleepingComputer reports that activity seen by administrators and researchers indicates remote code execution may also be possible, and eSentire calls such reports unconfirmed; per BleepingComputer, watchTowr says it reproduced the flaw but has not disclosed technical details.

Generic example of the CWE-119 weakness class; the actual root cause of CVE-2026-88779 has not been published:

Show code example(c)
// Copies data using a length taken from outside input, without checking the destination is big enough
memcpy(buf, input, input_len);

The fixed approach:

Show code example(c)
// Check the length fits in the buffer first; reject the request if it doesn't
if (input_len > sizeof(buf)) {
    return REJECT;
}
memcpy(buf, input, input_len);

Scoring differences: Citrix’s bulletin gives a CVSS 4.0 base score of 8.7, rated High; NVD gives a CVSS 3.1 score of 7.5 with availability-only impact (C:N/I:N/A:H). They use different CVSS versions, and both treat it as an availability-only issue. The 7.5 in this page’s severity field is NVD’s CVSS 3.1 score (the score from nvd@nist.gov marked Primary in the NVD API); the CNA (Citrix) gives CVSS 4.0 8.7 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N) in the CVE record and bulletin. Both scores are correct; they come from different scorers using different CVSS versions.

Timeline

DateEvent
Before the fix (exact date unknown)Customer appliances on 14.1-73.37 were repeatedly forced to reboot (BleepingComputer)
2026-10-02 (PlainCVE’s calculation)Attacks first reported. BleepingComputer says “Friday” and calls 10-04 Sunday in the same article, so we work out 10-02; the exact start of exploitation is unknown
2026-10-02 (per the press; the original publication time can’t be confirmed from the source)Citrix community post “Security Update Guidance for NetScaler SAML Authentication Deployments” describes the same issue: it is associated with deployments that use SAML authentication with Gateway or AAA functionality, and customers should check for add authentication samlAction or add authentication samlIdPProfile. The page shows only “Last Updated on: October 3, 2026” (Pacific Daylight Time), not an original publication date; BleepingComputer and eSentire report that Citrix published this notice on 10-02. Because the original publication time can’t be confirmed from the source, this page keeps 2026-10-03 as the first public disclosure date
2026-10-03 (Pacific time)Citrix publishes security bulletin CTX697174
2026-10-04 02:35 UTCCVE record published, which is the evening of 10-03 Pacific time, so it doesn’t conflict with Citrix’s date
2026-10-04CISA adds it to the Known Exploited Vulnerabilities catalog
2026-10-07KEV remediation due date for US federal agencies

Further reading

  • Zero-day: The Hacker News reports the flaw was exploited in targeted zero-day attacks, meaning before a fix existed; the press quotes Citrix as saying it observed targeted attacks on unmitigated deployments; the Canadian Centre for Cyber Security says Citrix indicates in-the-wild exploitation.
  • Malware on a honeypot: researcher Kevin Beaumont reported a downloaded malware binary running on one of his patched honeypots; it is not established that this CVE caused it. Separately, one administrator’s logs showed attempted exploitation and correlated crashes, but did not confirm that commands actually ran.
  • Ransomware: KEV lists known ransomware campaign use as Unknown.
  • When the flaw was introduced: not stated by the sources.
  • Detection rule: per Help Net Security, a threat hunter at Geico shared a SIGMA rule for spotting probing and exploitation attempts (not official).
  • Credits: Per the current Acknowledgement in Citrix bulletin CTX697174 (read 2026-10-12), Cloud Software Group thanks JPMorgan Chase, Bishop Fox and watchTowr. (watchTowr’s FAQ mentions only Bishop Fox and watchTowr.)
  • Related weakness type: CWE-119.

Verification Checked item by item against sources by AI under our review rules, all passed; not human-reviewed and not yet reproduced in our lab

AI review2026-10-12 · review rules

Verification records describe the environment and the result only, never reproduction steps or code that could attack other people’s systems. See our policy.

Sources

  1. AdvisoryCitrix NetScaler ADC and Citrix NetScaler Gateway Security Bulletin for CVE-2026-88779 (CTX697174) · Citrix (Cloud Software Group), 2026-10-03 · accessed 2026-10-12
  2. AdvisoryUnderstanding and addressing CVE-2026-88779 in Citrix NetScaler ADC and Citrix NetScaler Gateway · Citrix (Cloud Software Group), 2026-10-03 · accessed 2026-10-12
  3. AdvisorySecurity Update Guidance for NetScaler SAML Authentication Deployments · Citrix (Cloud Software Group) · accessed 2026-10-12
    The page shows only Last Updated on October 3, 2026 (Pacific Daylight Time), not an original publication date; the press reports it was published on 10-02, which can't be confirmed from the source
  4. CVE / NVD / OSVNVD API - CVE-2026-88779 · NIST · accessed 2026-10-07
  5. CVE / NVD / OSVCVE-2026-88779 record (CVE Services API) · CVE Program, 2026-10-04 · accessed 2026-10-07
  6. AdvisoryCitrix security advisory (AV26-996) · Canadian Centre for Cyber Security · accessed 2026-10-07
  7. NewsNew NetScaler zero-day exploited in attacks · The Hacker News · accessed 2026-10-07
  8. NewsCitrix patches NetScaler SAML zero-day exploited in attacks · BleepingComputer · accessed 2026-10-07
  9. NewsCitrix NetScaler CVE-2026-88779 (Help Net Security) · Help Net Security · accessed 2026-10-07
  10. NewsCitrix warns of actively exploited NetScaler flaw days after zero-day patch rush · CSO Online · accessed 2026-10-07
  11. ResearchCitrix NetScaler CVE-2026-88779 FAQ · watchTowr · accessed 2026-10-07
  12. ResearchActively exploited Citrix NetScaler ADC and NetScaler Gateway vulnerability (CVE-2026-88779) · eSentire · accessed 2026-10-07

Press brief

In one sentence

On October 3, 2026, Citrix published a security bulletin fixing CVE-2026-88779, a memory overflow in NetScaler ADC and NetScaler Gateway. Appliances configured for SAML sign-in can be crashed over the network by an attacker without an account. The US agency CISA added it to its Known Exploited Vulnerabilities catalog on October 4, and news reports say it was attacked before a fix existed. Appliances already upgraded for the previous batch of NetScaler flaws must be upgraded again if they meet the conditions.

Key facts

Severity (Citrix)
CVSS 4.0 8.7, High support.citrix.com
Severity (NVD)
CVSS 3.1 7.5, availability impact only services.nvd.nist.gov
Fixed versions
14.1-73.41, 13.1-64.28, 14.1-73.41 FIPS, 13.1-37.282 support.citrix.com
Bulletin published
2026-10-03 (Pacific time), CTX697174 support.citrix.com
CVE record published
2026-10-04 02:35 UTC cveawg.mitre.org
Credited to
JPMorgan Chase, Bishop Fox and watchTowr support.citrix.com

Confirmed

  • Citrix confirms it is a memory overflow leading to denial of service; its bulletin says the appliance must be configured as a SAML SP or IdP, and its blog says the issue is associated with deployments using SAML authentication with Gateway or AAA functionality.
  • It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-10-04), with a federal remediation due date of 2026-10-07.
  • The Canadian Centre for Cyber Security says Citrix indicates the flaw is exploited in the wild.

Unconfirmed / disputed

  • Whether it allows remote code execution: some reports suggest so, eSentire calls this unconfirmed; per BleepingComputer, watchTowr says it reproduced the flaw but has not disclosed technical details.
  • Whether 14.1-73.41 FIPS is fixed: Citrix says yes, but NVD's data lists it as affected.
  • When attacks began and when the flaw was introduced are not stated by the sources; KEV marks ransomware use as Unknown.

Quotable line

Appliances that had just been patched kept rebooting anyway; that is what a zero-day looks like: you did everything right, and the problem still found you.

Images

Download the share image (PNG) · Attack flow diagram (downloadable)

Please credit "PlainCVE" and link to this page. Full citation format is under "How to cite" below. Found a factual error? Report it.

How to cite this page

This article is CC BY 4.0. Please keep the attribution and link when republishing.

PlainCVE Team (2026). "NetScaler ADC and Gateway SAML memory overflow: attackers can crash the appliance without an account, exploited in the wild". PlainCVE. https://plaincve.date/en/vulns/cve-2026-88779-netscaler-saml-memory-overflow-dos (accessed YYYY-MM-DD)
BibTeX
@misc{cve202688779netscalersamlmemoryoverflowdos2026,
  title  = {NetScaler ADC and Gateway SAML memory overflow: attackers can crash the appliance without an account, exploited in the wild},
  author = {PlainCVE Team},
  year   = {2026},
  howpublished = {PlainCVE},
  url    = {https://plaincve.date/en/vulns/cve-2026-88779-netscaler-saml-memory-overflow-dos},
  note   = {Updated 2026-10-12}
}