Home / Companies / WorkOS / Blog / Post Details
Content Deep Dive

NetScaler's SAML zero-day: What CVE-2026-88779 means for anyone running SAML

Blog post from WorkOS

Post Details
Company
Date Published
Author
Maria Paktiti
Word Count
1,507
Company Posts That Month
36
Language
English
Hacker News Points
-
Post removed?
No
Summary

Citrix disclosed CVE-2026-88779 on October 3, 2026, an actively exploited SAML-related memory overflow affecting NetScaler ADC and Gateway appliances configured as SAML service providers or identity providers, and CISA added it to its Known Exploited Vulnerabilities catalog the following day with an October 7 federal patch deadline. Rated CVSS 8.7, the flaw is officially described as causing denial of service, although reports of compromised and rebooting appliances prompted concern that attackers may have used crashes to support exploitation of the separate pre-authentication command-injection flaw CVE-2026-88771; researchers who reproduced CVE-2026-88779 reported that it can crash systems but not directly execute code. Organizations using affected SAML configurations should upgrade to fixed NetScaler releases, including 14.1-73.41 or 13.1-64.28 and corresponding FIPS builds, even if they installed Citrix’s September 27 patches, while investigating unexpected reboots, authentication-process crashes, and related logs for possible compromise. The issue is the fourth SAML-dependent NetScaler vulnerability disclosed in 2026, highlighting the risks of processing unauthenticated XML before signature verification and reinforcing recommendations to keep SAML parsing minimal, use maintained libraries, constrain XML inputs, test endpoints, and establish secure contingency access procedures for identity-provider outages.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Platform Engineering 7 927 209 70 -45%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.