☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Citrix logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 🐛 CWE-119
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-88779

CVE-2026-88779 Vulnerability in Citrix
📅 PUBLISHED: 2026-10-04 00:00 UTC 🔄 UPDATED: 2026-10-05 14:42 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
🚨 ACTIVELY EXPLOITED (KEV) 💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.28%
👁️
0.28% probability
6.9× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: USA License: Commercial
VULNERABLE: Netscaler Application Delivery Controller
CVSS VECTOR BREAKDOWN 7.5
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: N Confidentiality None
I: N Integrity None
A: H Availability High
7.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-88779 is a vulnerability affecting Citrix NetScaler ADC (Application Delivery Controller) and NetScaler Gateway, the widely deployed application delivery and remote-access appliances that commonly sit at the enterprise network edge and are frequently exposed directly to the internet. The affected branch is defined strictly by version: ADC before 14.1-73.41, before 13.1-64.28, before 14.1-73.41 FIPS, and before 13.1-37.282; Gateway before 14.1-73.41 and before 13.1-64.28. Because the NVD description provides no root-cause detail, CWE mapping, CVSS score, or exploit information, the practical impact must be assessed conservatively: any unauthenticated flaw in these appliances is high-value, since NetScaler Gateways are a primary entry point into corporate remote-access infrastructure. Organizations running any affected build should treat this as a priority asset to inventory, isolate, and upgrade.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

The provided NVD entry is intentionally terse: it states only that a "Vulnerability in NetScaler ADC and NetScaler Gateway" exists and enumerates the affected version bands. There is no CNA narrative, no CWE classification, no CVSS metrics, and no description of the vulnerable component, protocol, or trigger condition. Per accuracy constraints, no implementation-level detail (function names, handlers, endpoints, or code paths) can be asserted, because none is present in the supplied data.

What can be established factually from the version alignment is the following. The advisory covers two product families that share a common code lineage: NetScaler ADC (the load-balancing/ADC role) and NetScaler Gateway (the SSL VPN / remote-access role). Both are exposed to identical fixed-version thresholds on the 14.1 and 13.1 branches, which is consistent with a shared underlying component rather than a feature unique to one role. The FIPS build of ADC is singled out at 14.1-73.41, indicating the FIPS branch carries its own build numbering. Notably, no 12.1 or 13.0 maintenance branch is named, implying the vendor's support baseline has moved to 13.1 and 14.1 only — older branches reaching end-of-life are not covered by the fix matrix and would remain permanently exposed.

NetScaler appliances operate in front of critical infrastructure and terminate TLS, so the attack surface is network-reachable by default on any deployment exposing the management or Gateway virtual servers to untrusted networks. Historically, vulnerabilities in this class of appliance have fallen into a small number of families — memory-safety flaws in the TLS/HTTP or authentication parsing path, authentication or authorization bypass in the Gateway/AAA layer, and injection-style flaws in request handling. Absent the CNA detail, this report does not assign the flaw to any one family; the vulnerability class is best treated as "network-reachable appliance flaw of unknown mechanism, fixed by version upgrade." Analysts should obtain the vendor advisory to determine whether the issue is pre-auth or post-auth, network or adjacent, and whether it enables code execution, authentication bypass, or information disclosure.

Because the appliance is edge-facing and often holds session tokens, VPN credentials, and inline access to internal applications, the confidentiality and integrity stakes are elevated regardless of the specific mechanism. A flaw reachable without credentials in this position typically yields a direct path toward internal lateral movement.

Exploitation Scenarios

No public proof-of-concept, Nuclei template, or exploit code exists in the supplied data, and no CVSS vector or CWE is provided. The attack chain below is therefore described at the vulnerability-class level and must not be read as a claim about specific code paths.

  1. Reconnaissance and target identification. An adversary enumerates internet-facing NetScaler ADC and Gateway instances using fingerprinting of the login/Gateway portal, TLS certificate metadata, and product-banner characteristics (see Shodan dorks). Version-dependent exposure is inferred from the affected build ranges; the goal is to identify unpatched appliances before any interaction with the application layer.

  2. Trigger of the flaw class. Because the mechanism is unspecified, the plausible triggers correspond to the standard edge-appliance vulnerability classes: a crafted request to a network-exposed service that exercises a memory-safety condition, an authentication/authorization check in the Gateway or AAA path, or a request-parsing/injection condition. The trigger is delivered over the exposed network service. No specific endpoint, parameter, or payload is asserted here, as none is derivable from the provided description.

  3. Execution method. At the vulnerability-class level, exploitation would proceed by sending a crafted request to the exposed service that violates the intended processing or trust assumption. If the flaw is pre-authentication, no credentials are required; if post-authentication, a low-privileged session may suffice. In either case the delivery vector is direct network traffic to the appliance interface, which is why exposure reduction (restricting the management interface and limiting the Gateway to intended clients) is the most immediate control.

  4. Post-exploitation impact. Depending on mechanism — which the vendor advisory must clarify — outcomes range from information disclosure (session tokens, configuration, credentials) to authentication bypass and, in the worst case, code execution on the appliance. An appliance that terminates VPN and application traffic can then be used to pivot into internal resources, harvest credentials, or manipulate traffic. No threat-actor attribution or in-the-wild evidence is available in the supplied data.

Impact Assessment

No CVSS base score or subscores are provided; EPSS has not been assigned by FIRST.org, and the CVE is not listed in CISA KEV. Impact must therefore be reasoned from asset criticality rather than metrics.

Affected systems: Citrix NetScaler ADC at versions before 14.1-73.41 and before 13.1-64.28 (plus the 14.1-73.41 FIPS branch and 13.1-37.282), and NetScaler Gateway before 14.1-73.41 and before 13.1-64.28. Any environment relying on these appliances for load balancing, TLS termination, or remote access is in scope.

Blast radius: these devices are typically deployed at the perimeter and mediate traffic for large numbers of internal applications and users. Compromise of a single appliance can expose every session and backend route it brokers, giving disproportionate leverage relative to a single-host breach. Where the Gateway role is used for SSL VPN, the appliance may itself hold or relay credentials and multi-factor material.

Business impact: potential loss of confidentiality (session and credential exposure), integrity (traffic manipulation, unauthorized access), and availability (denial of service or forced outage during incident response). Regulatory exposure follows if the appliance fronts systems handling regulated data. Because the flaw is unpatched in the tracking sources (patch confidence 0/4), residual risk remains until the fixed builds are applied and verified.

Detection Guidance

Sigma Rule

title: Suspicious HTTP Requests Targeting Citrix NetScaler ADC/Gateway (CVE-2026-88779)
id: 3f9c1b7e-8877-4c9b-9f21-26a1b7c9d001
status: experimental
description: Detects anomalous request patterns directed at exposed NetScaler ADC/Gateway services; tuning required as the exact exploit vector for CVE-2026-88779 is not publicly documented.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-88779
author: valtersit.com
date: 2026-01-01
logsource:
  category: webserver
detection:
  selection_product:
    cs-uri-stem|contains:
      - '/vpn/'
      - '/nitro/'
      - '/gw/'
  selection_suspicious:
    cs-uri-query|contains:
      - '../'
      - '..%2f'
      - '${'
      - '%00'
      - 'cmd='
  filter_admin:
    c-ip|cidr:
      - '10.0.0.0/8'
      - '172.16.0.0/12'
      - '192.168.0.0/16'
  condition: selection_product and selection_suspicious and not filter_admin
falsepositives:
  - Authorized penetration testing
  - Legitimate administrative access from non-standard networks
level: medium

YARA Rule

rule CVE_2026_88779_NetScaler_Exploit_Artifacts
{
    meta:
        description = "Detects generic exploit artifacts referencing NetScaler ADC/Gateway, tailoring required; no public PoC available for CVE-2026-88779"
        author = "valtersit.com"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-88779"
        date = "2026-01-01"
        severity = "medium"
    strings:
        $p1 = "NetScaler" ascii nocase
        $p2 = "Citrix Gateway" ascii nocase
        $p3 = "CVE-2026-88779" ascii nocase
        $e1 = "/vpn/" ascii
        $e2 = "/nitro/" ascii
        $mz = { 4D 5A }
    condition:
        (uint16(0) == 0x5A4D or $p1 or $p2) and any of ($e*) and $mz
}

Suricata IDS Rule

alert http any any -> any any (msg:"CVE-2026-88779 Possible NetScaler ADC/Gateway Exploitation Attempt"; flow:established,to_server; http.uri; content:"/vpn/"; http.uri; content:".."; msg:"path traversal attempt against NetScaler"; classtype:attempted-admin; sid:2026887790; rev:1; metadata:reference nvd,CVE-2026-88779;)

Elastic Detection

sequence by source.ip with maxspan=30s
  [ network where network.protocol == "http" and
      url.path : ("/vpn/*", "/nitro/*", "/gw/*") and
      url.query : ("*../*", "*%2f*", "*%00*", "*${*") ]

Splunk SPL Query

index=web OR index=proxy
| search (uri="/vpn/*" OR uri="/nitro/*" OR uri="/gw/*")
| search (uri="*../*" OR uri="*%2f*" OR uri="*%00*" OR uri="*${*")
| stats count min(_time) as first_seen max(_time) as last_seen by src_ip uri http_user_agent
| where count > 3
| sort - count

Wazuh OSSEC Rule

<group name="web,citrix,">
  <rule id="202688779" level="10">
    <decoded_as>web-accesslog</decoded_as>
    <match>/vpn/|/nitro/|/gw/</match>
    <regex>\.\./|%2f|%00|\$\{</regex>
    <description>CVE-2026-88779: Suspicious request targeting Citrix NetScaler ADC/Gateway may indicate exploitation attempt</description>
    <mitre>
      <id>T1190</id>
    </mitre>
  </rule>
</group>

Mitigation & Patch Guidance

Patch confidence: 0/4 (UNPATCHED — no patch evidence from any tracked source). No vendor workaround and no confirmed patch reference were supplied; the following reflects standard practice for edge-appliance vulnerabilities and must be validated against the authoritative vendor advisory.

  1. Immediate mitigations
  • Inventory every NetScaler ADC and Gateway instance and map each to its branch and build; flag anything below the fixed thresholds (ADC 14.1-73.41 / 13.1-64.28 / 14.1-73.41 FIPS / 13.1-37.282; Gateway 14.1-73.41 / 13.1-64.28).
  • Restrict management interfaces (NSIP/management GUI/CLI) from the public internet; allow only trusted administrative networks.
  • Where operationally feasible, limit internet exposure of Gateway virtual servers to expected client geography/ASNs and require strong MFA at the identity provider.
  • Increase logging and monitoring at the appliance and upstream WAF/IDS for the request anomaly patterns above, and preserve PCAPs for triage.
  • Treat unsupported 12.1/13.0 branches as permanently exposed; plan migration.
  1. Patch/upgrade steps
  • Obtain the official vendor advisory and confirm which branch fix corresponds to the deployment. Upgrade ADC and Gateway to at least: ADC 14.1-73.41 or 13.1-64.28 (and the matching FIPS build 14.1-73.41); Gateway 14.1-73.41 or 13.1-64.28.
  • Follow the vendor's upgrade sequence for HA pairs (upgrade secondary, test failover, then primary) and validate post-upgrade configuration.
  • After upgrade, verify build numbers on all appliances, including any appliances previously missed in inventory.
  1. Long-term hardening
  • Adopt a rapid patch cadence for perimeter appliances with tracked SLAs for critical edge assets.
  • Enforce least-privilege and short-lived credentials on the Gateway path; centralize identity and MFA.
  • Segment management networks from data/application networks and apply egress filtering from the appliance.
  • Continuously monitor for new advisories affecting NetScaler ADC/Gateway and subscribe to vendor security notifications.

References

No threat actor campaign, in-the-wild exploitation evidence, or public proof-of-concept is available in the supplied intelligence for CVE-2026-88779. Any specific technical detail beyond the affected version ranges was not provided by the CNA/NVD description and has not been asserted.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

product:"Citrix"
title:"Citrix"
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-88779/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.