dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-4368

HIGH · 7.7 CVSS v4.0 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Race Condition in NetScaler ADC and NetScaler Gateway when appliance is configured as Gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server leading to User Session Mixup

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A race condition exists in NetScaler ADC and NetScaler Gateway when configured as a Gateway virtual server (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server. This vulnerability can cause user session mixup, potentially allowing one user to access or interact with another user's session.

MitigationApply the vendor-provided patch for CVE-2026-4368. If a patch is unavailable, consider restricting access to affected Gateway and AAA virtual server configurations pending remediation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetScaler deployment type
    Confirm whether NetScaler ADC or NetScaler Gateway is deployed in your environment by checking the system information or license details.
    Affected if The system is running NetScaler ADC or NetScaler Gateway software.
  2. Check for Gateway virtual server configuration
    Use the NetScaler command line (show vserver) or GUI to list all configured virtual servers and identify any with type SSL VPN, ICA Proxy, CVPN, or RDP Proxy.
    Affected if A Gateway virtual server is configured with SSL VPN, ICA Proxy, CVPN, or RDP Proxy service type.
  3. Check for AAA virtual server configuration
    Use the NetScaler command line (show aaa vserver) or GUI to list all AAA virtual servers configured on the system.
    Affected if One or more AAA virtual servers are configured on the NetScaler appliance.
  4. Verify active session handling
    Review session logs or use the NetScaler command (show session) during peak usage to observe whether multiple user sessions are being processed concurrently on affected virtual servers.
    Affected if Users report experiencing sessions belonging to other users or unexpected session behavior on Gateway or AAA virtual servers.

Your environment is affected if you run NetScaler ADC or NetScaler Gateway with any Gateway virtual server (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server configured, as the race condition only triggers when these specific configurations are active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patch for CVE-2026-4368. If a patch is unavailable, consider restricting access to affected Gateway and AAA virtual server configurations pending remediation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4368 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data