CVE-2020-1938: Ghostcat
- Vendors
- Oracle CorporationNetAppDebian ProjectFedora ProjectApache Software FoundationBlackberryOpensuse
Ghostcat is a file read/inclusion vulnerability in Apache Tomcat's Apache JServ Protocol (AJP) connector affecting versions 9.0.0.M1–9.0.0.30, 8.5.0–8.5.50, and 7.0.0–7.0.99. These releases enabled AJP by default and bound it to all configured IP addresses. Tomcat's elevated trust in AJP connections allows an attacker who can reach the connector to retrieve arbitrary files within a web application or cause web-application files to be processed as JavaServer Pages (JSP). If the attacker can upload or otherwise control file content within the web application, JSP processing can enable remote code execution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthenticated attackers with AJP access can disclose web-application source code, configuration, credentials, and other sensitive application files. File disclosure is scoped to the web application, rather than unrestricted filesystem access. Where attackers can place controlled content within the application, exploitation can execute arbitrary code with the Tomcat process's privileges, compromising application data and service integrity and availability.
Mitigation
If you can’t patch tonight, do this now.
Disable the AJP connector when unnecessary and use HTTP or HTTPS for proxy-to-application communication instead. If AJP must remain enabled, restrict its bind address and firewall access to trusted proxy hosts and configure a strong shared secret on both the connector and compatible front-end proxies. Update dependent proxy configurations before disabling AJP to avoid service disruption. Do not expose AJP to untrusted networks.
Remediation
Patch, then assume compromise.
Upgrade to a supported Tomcat release containing the fix. The first fixed releases are 9.0.31, 8.5.51, and 7.0.100. For vendor-packaged or embedded Tomcat and JBoss Web deployments, install the applicable vendor security update, which may backport the fix without adopting these upstream version numbers. Review AJP connector and front-end proxy configuration after updating because hardened defaults may require configuration changes. Restart the affected service as required for the update to take effect.
Exploits
18 exploits validated by Mallory's analysis. Hidden: 9 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2020-1938 exploited in the wild?
- Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
- Is there a public exploit for CVE-2020-1938?
- Yes. Mallory tracks 18 public exploits or proofs of concept for CVE-2020-1938, the earliest disclosed Feb 20, 2020.
- Is there a patch for CVE-2020-1938?
- Upgrade to a supported Tomcat release containing the fix. The first fixed releases are 9.0.31, 8.5.51, and 7.0.100.
- What products are affected by CVE-2020-1938?
- Apache Software Foundation Tomcat, Oracle Corporation Agile Engineering Data Management, Oracle Corporation Agile Plm, Oracle Corporation Agile Product Lifecycle Management, Oracle Corporation Communications Element Manager, and at least 17 more.
- How severe is CVE-2020-1938?
- CVE-2020-1938 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 99.3% (100th percentile) as of Oct 25, 2026.
Recent activity
46 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.