CVE-2025-6543
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 · uneditedMemory overflow vulnerability leading to unintended control flow and Denial of Service in NetScaler ADC and NetScaler Gateway when configured as Gateway (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) OR AAA virtual server
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 confidenceA memory overflow vulnerability in Citrix NetScaler ADC and NetScaler Gateway allows attackers to cause unintended control flow and denial of service when the appliance is configured as a Gateway (supporting VPN virtual server, ICA Proxy, CVPN, or RDP Proxy) or an AAA virtual server. The critical CVSS 9.8 suggests potential for remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 13.1, < 13.1-37.236>= 13.1, < 13.1-59.19>= 14.1, < 14.1-47.46>= 13.1, < 13.1-59.19>= 14.1, < 14.1-47.46CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetScaler product type and versionRun `show version` on the NetScaler command line or check the GUI under System > Information > Version. Note whether it is NetScaler ADC or NetScaler Gateway.Affected if The installed version is 13.1 build 37.235 or lower, 13.1 build 59.18 or lower, or 14.1 build 47.45 or lower.
-
Verify Gateway virtual server configurationRun `show vpn vserver` to list all VPN virtual servers. Check for configured virtual servers with VPN, ICA Proxy, CVPN, or RDP Proxy type enabled.Affected if Any VPN virtual server, ICA Proxy, CVPN, or RDP Proxy is actively configured on the device.
-
Verify AAA virtual server configurationRun `show aaa vserver` to list all AAA virtual servers. Check for any actively configured AAA virtual servers.Affected if Any AAA virtual server is configured on the device.
-
Confirm the device is exposed to untrusted networksReview the bound IP address and access control lists for the Gateway or AAA virtual servers identified in previous steps. Check `show run` output for interface bindings.Affected if The Gateway or AAA virtual server is bound to a publicly accessible IP address or accepts connections from untrusted networks.
The environment is affected if the NetScaler runs a vulnerable version (13.1 before build 59.19 or 14.1 before build 47.46) AND has a Gateway virtual server (VPN, ICA Proxy, CVPN, or RDP Proxy) or AAA virtual server configured and exposed.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped13.1-37.23613.1-59.1914.1-47.46
Apply the vendor-released patch or upgrade to a supported NetScaler ADC/Gateway version that addresses this vulnerability. Review and harden Gateway and AAA virtual server configurations if immediate patching is not feasible.
Upgrade to NetScaler 13.1-59.19 or later, or 14.1-47.46 or later
- 1. Identify the current NetScaler ADC or Gateway version by running 'show version' or checking the GUI dashboard
- 2. Confirm the deployment uses Gateway (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server configuration, as only these configurations are affected
- 3. Schedule a maintenance window as the upgrade will require a brief service interruption
- 4. Download the appropriate build from Citrix support: version 13.1-59.19 or later for 13.1 releases, or version 14.1-47.46 or later for 14.1 releases
- 5. Back up the current NetScaler configuration using 'save ns config' and export the ns.conf file
- 6. Upload the new firmware build via the NetScaler GUI (System > Firmware) or CLI
- 7. Install the firmware and restart the NetScaler device
- 8. After reboot, verify the new version is running with 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6543 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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