Apache Tomcat: Configured cipher preference order not preserved
Published 9 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.tomcat:tomcat-coyote?
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.114 <9.0.116
- Fixed in
- 9.0.116
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=9.0.116 -DforceVersion=true- Affected
- >=10.1.51 <10.1.53
- Fixed in
- 10.1.53
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=10.1.53 -DforceVersion=true- Affected
- >=11.0.16 <11.0.20
- Fixed in
- 11.0.20
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=11.0.20 -DforceVersion=true- Affected
- >=9.0.114 <9.0.116
- Fixed in
- 9.0.116
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=9.0.116 -DforceVersion=true- Affected
- >=10.1.51 <10.1.53
- Fixed in
- 10.1.53
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=10.1.53 -DforceVersion=true- Affected
- >=11.0.16 <11.0.20
- Fixed in
- 11.0.20
mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat -DdepVersion=11.0.20 -DforceVersion=true- Affected
- >=9.0.114 <9.0.116
- Fixed in
- 9.0.116
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=9.0.116 -DforceVersion=true- Affected
- >=10.1.51 <10.1.53
- Fixed in
- 10.1.53
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=10.1.53 -DforceVersion=true- Affected
- >=11.0.16 <11.0.20
- Fixed in
- 11.0.20
mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=11.0.20 -DforceVersion=trueDetails
Configured cipher preference order not preserved vulnerability in Apache Tomcat.
This issue affects Apache Tomcat: from 11.0.16 through 11.0.18, from 10.1.51 through 10.1.52, from 9.0.114 through 9.0.115.
Users are recommended to upgrade to version 11.0.20, 10.1.53 or 9.0.116, which fix the issue.
Is GHSA-69cc-cv78-qc8g 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-coyote, and gives you the command that fixes it.
More advisories for org.apache.tomcat:tomcat-coyote
- CriticalCVE-2026-65637Apache Tomcat - HTTP/2 no-authority bypass of strict SNI validation · 26 Aug 2026
- CriticalCVE-2026-41293Apache Tomcat - HTTP/2 request headers not validated · 12 May 2026
- HighCVE-2026-24880Apache Tomcat has an HTTP Request/Response Smuggling vulnerability · 9 Apr 2026
- MediumCVE-2026-32990Apache Tomcat has an Improper Input Validation vulnerability · 9 Apr 2026
- HighCVE-2026-24734Apache Tomcat has an Improper Input Validation vulnerability · 17 Feb 2026
- MediumCVE-2025-66614Apache Tomcat - Client certificate verification bypass · 17 Feb 2026
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-29129
- Linkgithub.com/apache/tomcat/commit/5cfa876d73f1ff5f4dc8309c4320f684cbeff74e
- Linkgithub.com/apache/tomcat/commit/6db238562ec36ab1106db4d04843f8b33e7a0c06
- Linkgithub.com/apache/tomcat/commit/8d69b33764dba81dce89e3a768de6093a35620ae
- Packagegithub.com/apache/tomcat
- Linklists.apache.org/thread/r4h1t6f8xhxsxfm6c2z5cprolsosho3f
- Linktomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.53
- Linktomcat.apache.org/security-11.html#Fixed_in_Apache_Tomcat_11.0.20
- Linktomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.116
- Linkwww.openwall.com/lists/oss-security/2026/04/09/22
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.