# CVE-2019-19781: Citrix ADC, Gateway, and SD-WAN WANOP Appliance Code Execution

> Attackers can exploit directory traversal in Citrix ADC and Gateway to execute arbitrary code or read sensitive data.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2019
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-jjcm-f6q3-w5xj

## What is CVE-2019-19781?

CVE-2019-19781 is a critical path traversal vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Citrix Application Delivery Controller (ADC) and Gateway 10.5, 11.1, 12.0, 12.1, and 13.0. They allow Directory Traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-19781?

It affects 3 products.


Products: Citrix Application Delivery Controller Firmware, Citrix Gateway Firmware, Citrix Netscaler Gateway Firmware.

## How do I fix CVE-2019-19781?

No fix has been published for CVE-2019-19781 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-19781 being exploited?

Yes. Attackers have exploited CVE-2019-19781 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- This is a tool published for the Citrix ADC (NetScaler) vulnerability. We are only disclosing this due to others publishing the exploit code first. (github_poc): https://github.com/trustedsec/cve-2019-19781
- Remote Code Execution Exploit for Citrix Application Delivery Controller and Citrix Gateway [ CVE-2019-19781 ] (github_poc): https://github.com/projectzeroindia/CVE-2019-19781
- CVE-2019-19781 - Remote Code Execution on Citrix ADC Netscaler exploit (github_poc): https://github.com/mpgn/CVE-2019-19781
- Detect and log CVE-2019-19781 scan and exploitation attempts. (github_poc): https://github.com/MalwareTech/CitrixHoneypot
- Test a host for susceptibility to CVE-2019-19781 (github_poc): https://github.com/cisagov/check-cve-2019-19781
- Indicator of Compromise Scanner for CVE-2019-19781 (github_poc): https://github.com/mandiant/ioc-scanner-CVE-2019-19781

## Other vulnerabilities in n/a

- [CVE-2022-27518](https://insights.sbomify.com/CVE-2022-27518/): Citrix Application Delivery Controller (ADC) and Gateway Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-8193](https://insights.sbomify.com/CVE-2020-8193/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Authorization Bypass (medium 6.5, exploited in the wild)
- [CVE-2020-8195](https://insights.sbomify.com/CVE-2020-8195/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure (medium 6.5, exploited in the wild)
- [CVE-2020-8196](https://insights.sbomify.com/CVE-2020-8196/): Citrix ADC, Gateway, and SD-WAN WANOP Appliance Information Disclosure (medium 4.3, exploited in the wild)
- [CVE-2022-27510](https://insights.sbomify.com/CVE-2022-27510/): Unauthorized access to Gateway user capabilities (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19781 and fix it if it is affected.

What it is: CVE-2019-19781 is a critical path traversal vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-19781 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-19781/ (Markdown: https://insights.sbomify.com/CVE-2019-19781/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-19781
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-19781
- OSV: https://osv.dev/vulnerability/CVE-2019-19781

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-19781/
Summaries are generated and may contain mistakes; the official description above is the record.