dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jan 2023.
Application Delivery Controller FirmwareOperating system · Citrix

CVE-2022-27518

CRITICAL · 9.8 CVSS v3.1 Developing Published 2022-12-13
Fix available
A fix is available. Upgrade to 12.1-55.291 / 12.1-65.25 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges 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
Unauthenticated remote arbitrary code execution

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-22.

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
Application Delivery Controller FirmwareOperating system
Affected:>= 12.1, < 12.1-55.291>= 12.1, < 12.1-65.25>= 13.0, < 13.0-58.32
Gateway FirmwareOperating system
Affected:>= 12.1, < 12.1-65.25>= 13.0, < 13.0-58.32

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
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

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 · scoped
Upgrade available Upgrade to 12.1-55.291 / 12.1-65.25 / 13.0-58.32 or later
Fixed in 12.1-55.29112.1-65.2513.0-58.32
Recommended fix High confidence

Citrix ADC/Gateway firmware 12.1-65.25 or later (for 12.1.x); 13.0-58.32 or later (for 13.0.x)

  1. 1. Identify the current Citrix ADC or Gateway firmware version by navigating to the System > Information > Diagnostics page in the management GUI or running 'show version' in the CLI
  2. 2. Download the appropriate firmware build from the Citrix support portal (support.citrix.com) - select build 12.1-65.25 or later for 12.1.x versions, or build 13.0-58.32 or later for 13.0.x versions
  3. 3. Back up the current appliance configuration using 'save ns config' in CLI or via the GUI (System > Backup and Restore > Create Backup)
  4. 4. If running a HA pair, upgrade the secondary node first and verify it comes up successfully
  5. 5. Perform a firmware upgrade: navigate to System > Firmware > Upgrade in the GUI, or use 'install firmware' command in the CLI
  6. 6. After upgrade completes, verify the new version by running 'show version' and confirm it matches the expected fixed build
  7. 7. For HA pairs, perform a forced failover to the upgraded secondary and repeat the upgrade process on the primary node
  8. 8. Verify all services are functioning normally and test critical application functionality
Caveat Review Citrix release notes for the target build for any configuration or behavioral changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27518 — 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-2022-27518 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