Citrix NetScaler ADC (formerly Citrix ADC) and Citrix NetScaler Gateway (formerly Citrix Gateway) contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for a denial of service.
NetScaler ADC and NetScaler Gateway contain a memory buffer overflow in their SAML processing code. A remote, unauthenticated attacker can send a crafted SAML message to an affected appliance configured as a SAML service provider or identity provider, crashing the service and causing a denial of service. Citrix has confirmed targeted attacks against unmitigated deployments. Affected versions span the 13.1 and 14.1 release lines, including FIPS and NDcPP builds.
CWE-119 describes a condition where software reads or writes memory outside the boundaries of an allocated buffer. In NetScaler ADC and Gateway, the flaw resides in the code path that parses inbound SAML messages. When the appliance is configured as a SAML service provider or identity provider, it accepts SAML requests and responses from external parties before any authentication check occurs. A malformed message can cause the parser to operate outside its allocated buffer, corrupting memory state and crashing the affected service. Repeated triggering keeps the service unavailable.
An attacker with network access to the SAML endpoint sends a crafted SAML request or response. No credentials and no user interaction are required. The precondition is that the target appliance must be configured with either an authentication SAML action (SAML SP) or a SAML IdP profile. When that condition is met, the overflow is reachable from the network. The result is denial of service: the NetScaler ADC or Gateway service becomes unavailable. Citrix states no impact on data confidentiality or integrity, and has confirmed targeted attacks against unmitigated deployments.
This vulnerability is confirmed as actively exploited in the wild — it is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
If Citrix NetScaler runs inside your authorization boundary, yes. CVE-2026-88779 appears in CISA's Known Exploited Vulnerabilities (KEV) catalog, carrying a remediation deadline of October 7, 2026. For a FedRAMP-authorized service, an unpatched KEV within the boundary is an assessor finding. You must either remediate the vulnerability or formally document a mitigation before your assessor and sponsoring agency raise it during review.
Knox does not patch your Citrix NetScaler deployment. Under the FedRAMP shared-responsibility model, that remediation is yours to execute. What Knox provides is the pre-authorized, single-tenant boundary to remediate within, along with continuous compliance monitoring and audit-artifact coverage to document the fix for your next assessment. The work of applying the patch stays with your team; managing compliance posture while you do it does not have to.
Knox's automated continuous monitoring platform watches your environment for newly disclosed vulnerabilities and compliance issues on an ongoing basis. For a KEV like CVE-2026-88779, that means exposure surfaces during continuous monitoring rather than waiting until an assessor flags it at a scheduled review.
Knox runs a FedRAMP-as-a-Service platform. It gives SaaS vendors a pre-authorized cloud boundary on AWS, Azure, and GCP. Your application inherits 60-80% of the required security controls. You reach FedRAMP authorization in about 90 days for roughly 90% less than the traditional $3.5M path. Book a meeting and Knox will map your path to authorization.
An unremediated CVE-2026-88779 becomes a Plan of Action and Milestones (POA&M) item. A growing POA&M list is precisely what turns a routine continuous-monitoring review into a difficult conversation with your sponsoring agency. Closing the item out and documenting the remediation is what keeps your authorization clean and the agency relationship intact.
Schedule a meeting to discuss scope, parse readiness, and map your company’s accelerated path to FedRAMP authorization.









_Horizontal_RGB.png)








