CVE-2026-29129

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.

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

CVE-2026-29129 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.116, 10.1.53, 11.0.20); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-29129? CVE-2026-29129 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 9.0.114, < 9.0.116. It is fixed in 9.0.116, 10.1.53, 11.0.20. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
2. How severe is CVE-2026-29129? CVE-2026-29129 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-29129?
   • org.apache.tomcat:tomcat (maven) (versions >= 9.0.114, < 9.0.116)
   • org.apache.tomcat.embed:tomcat-embed-core (maven) (versions >= 9.0.114, < 9.0.116)
   • org.apache.tomcat:tomcat-coyote (maven) (versions >= 9.0.114, < 9.0.116)
4. Is there a fix for CVE-2026-29129? Yes. CVE-2026-29129 is fixed in 9.0.116, 10.1.53, 11.0.20. Upgrade to this version or later.
5. Is CVE-2026-29129 exploitable, and should I be worried? Whether CVE-2026-29129 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-29129 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-29129?
   • Upgrade org.apache.tomcat:tomcat to 9.0.116 or later
   • Upgrade org.apache.tomcat:tomcat to 10.1.53 or later
   • Upgrade org.apache.tomcat:tomcat to 11.0.20 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 9.0.116 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 10.1.53 or later
   • Upgrade org.apache.tomcat.embed:tomcat-embed-core to 11.0.20 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 9.0.116 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 10.1.53 or later
   • Upgrade org.apache.tomcat:tomcat-coyote to 11.0.20 or later