Apache Tomcat vulnerable to Insertion of Sensitive Information into Log File
Published 9 Apr 2026 · Updated 11 Sept 2026
Is your project on an affected org.apache.tomcat:tomcat-tribes?
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.13 <9.0.117
- Fixed in
- 9.0.117
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-tribes -DdepVersion=9.0.117 -DforceVersion=true- Affected
- >=10.1.0-M1 <10.1.54
- Fixed in
- 10.1.54
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-tribes -DdepVersion=10.1.54 -DforceVersion=true- Affected
- >=11.0.0-M1 <11.0.21
- Fixed in
- 11.0.21
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-tribes -DdepVersion=11.0.21 -DforceVersion=true- Affected
- >=9.0.13 <9.0.117
- Fixed in
- 9.0.117
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=9.0.117 -DforceVersion=true- Affected
- >=10.1.0-M1 <10.1.54
- Fixed in
- 10.1.54
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=10.1.54 -DforceVersion=true- Affected
- >=11.0.0-M1 <11.0.21
- Fixed in
- 11.0.21
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=11.0.21 -DforceVersion=true- Affected
- >=9.0.13 <9.0.117
- Fixed in
- 9.0.117
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=9.0.117 -DforceVersion=true- Affected
- >=10.1.0-M1 <10.1.54
- Fixed in
- 10.1.54
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=10.1.54 -DforceVersion=true- Affected
- >=11.0.0-M1 <11.0.21
- Fixed in
- 11.0.21
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=11.0.21 -DforceVersion=trueDetails
Insertion of Sensitive Information into Log File vulnerability in the cloud membership for clustering component of Apache Tomcat exposed the Kubernetes bearer token.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.13 through 9.0.116.
Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fix the issue.
Is GHSA-x4m4-345f-5h5g 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:tomcat-tribes, and gives you the command that fixes it.
More advisories for org.apache.tomcat:tomcat-tribes
- MediumCVE-2026-55955Apache Tomcat has an Improper Authentication vulnerability · 29 Jun 2026
- HighCVE-2026-34486Apache Tomcat Missing Encryption of Sensitive Data vulnerability · 9 Apr 2026
- HighCVE-2026-29146Apache Tomcat: Padding Oracle vulnerability in EncryptInterceptor · 9 Apr 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-34487
- Linkgithub.com/apache/tomcat/commit/301bc6efbf72feb14dacfdfa3f50372182736150
- Linkgithub.com/apache/tomcat/commit/5eff2a773b8b728083e5195b3183df1b9e12a03d
- Linkgithub.com/apache/tomcat/commit/f593292a082e5ef9336a8db2b4b522f7f3e36976
- Packagegithub.com/apache/tomcat
- Linklists.apache.org/thread/4xpkwolpkrj8v5xzp5nyovtlqp3y850h
- Linktomcat.apache.org/security-10.html
- Linktomcat.apache.org/security-11.html
- Linktomcat.apache.org/security-9.html
- Linkwww.openwall.com/lists/oss-security/2026/04/09/28
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.