CriticalGHSA-c9hw-wf7x-jp9jBIT-tomcat-2020-1938CVE-2020-1938

Improper Privilege Management in Tomcat

Published 15 Jun 2020 · Updated 7 Aug 2026

Is your project on an affected org.apache.tomcat.embed:tomcat-embed-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=9.0.0 <9.0.31
Fixed in
9.0.31
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=9.0.31 -DforceVersion=true
Affected
>=8.0.0 <8.5.51
Fixed in
8.5.51
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=8.5.51 -DforceVersion=true
Affected
>=7.0.0 <7.0.100
Fixed in
7.0.100
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=7.0.100 -DforceVersion=true

Details

When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: returning arbitrary files from anywhere in the web application, processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.

Is GHSA-c9hw-wf7x-jp9j in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.tomcat.embed:tomcat-embed-core, and gives you the command that fixes it.

More advisories for org.apache.tomcat.embed:tomcat-embed-core

  • CriticalCVE-2026-65905Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability · 26 Aug 2026
  • CriticalCVE-2026-65637Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation · 26 Aug 2026
  • CriticalCVE-2026-65182Apache Tomcat has an Improper Access Control, Incorrect Authorization vulnerability · 26 Aug 2026
  • CriticalCVE-2026-68525Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability · 26 Aug 2026
  • CriticalCVE-2026-55276Apache Tomcat has an Always-Incorrect Control Flow Implementation vulnerability · 29 Jun 2026
  • HighCVE-2026-55957Apache Tomcat has a Missing Critical Step in Authentication vulnerability · 29 Jun 2026
All 82 advisories for org.apache.tomcat.embed:tomcat-embed-core

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.