CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in apache tomcat. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.tomcat:tomcat-coyote 10.1.53, 11.0.20, 9.0.116.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Norg.apache.tomcat:tomcat-coyote (Maven): fixed in 9.0.116, 10.1.53, 11.0.20org.apache.tomcat:tomcat (Maven): fixed in 9.0.116, 10.1.53, 11.0.20org.apache.tomcat.embed:tomcat-embed-core (Maven): fixed in 9.0.116, 10.1.53, 11.0.20Explain CVE-2026-29129 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-29129?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-29129?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-29129 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Tomcat | from 11.0.16 through 11.0.18 |
| Apache Software Foundation Apache Tomcat | from 10.1.51 through 10.1.52 |
| Apache Software Foundation Apache Tomcat | from 9.0.114 through 9.0.115 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat-coyote | >=9.0.114 <9.0.116 | 9.0.116 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat-coyote | >=10.1.51 <10.1.53 | 10.1.53 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat-coyote | >=11.0.16 <11.0.20 | 11.0.20 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat | >=9.0.114 <9.0.116 | 9.0.116 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat | >=10.1.51 <10.1.53 | 10.1.53 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat:tomcat | >=11.0.16 <11.0.20 | 11.0.20 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat.embed:tomcat-embed-core | >=9.0.114 <9.0.116 | 9.0.116 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat.embed:tomcat-embed-core | >=10.1.51 <10.1.53 | 10.1.53 |
| GHSA-69cc-cv78-qc8g | Maven | org.apache.tomcat.embed:tomcat-embed-core | >=11.0.16 <11.0.20 | 11.0.20 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | tomcat10 | 10.1.55-1~deb12u1 | DEBIAN-CVE-2026-29129 |
| Debian | 12, 13, 14 | tomcat9 | 9.0.70-2 | DEBIAN-CVE-2026-29129 |
| Debian | 13 | tomcat10 | 10.1.55-1~deb13u1 | DEBIAN-CVE-2026-29129 |
| Debian | 13 | tomcat11 | 11.0.22-1~deb13u1 | DEBIAN-CVE-2026-29129 |
| Debian | 14 | tomcat10 | 10.1.54-1 | DEBIAN-CVE-2026-29129 |
| Debian | 14 | tomcat11 | 11.0.21-1 | DEBIAN-CVE-2026-29129 |
| Ubuntu | 26.04:LTS | tomcat11 | no fix listed | UBUNTU-CVE-2026-29129 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 more | tomcat | 9.0.117-150200.105.1 | SUSE-SU-2026:1604-1 |
| SUSE | Linux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Module for Web and Scripting 15 SP7 and 4 more | tomcat10 | 10.1.54-150200.5.64.1 | SUSE-SU-2026:1603-1 |
| SUSE | Linux Enterprise Module for Web and Scripting 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | tomcat11 | 11.0.21-150600.13.18.1 | SUSE-SU-2026:1558-1 |
| SUSE | Linux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5 | tomcat | 9.0.117-3.163.2 | SUSE-SU-2026:1572-1 |
| openSUSE | Leap 16.0 | tomcat | 9.0.117-160000.1.1 | openSUSE-SU-2026:20611-1 |
| openSUSE | Leap 16.0 | tomcat10 | 10.1.54-160000.1.1 | openSUSE-SU-2026:20612-1 |
| openSUSE | Leap 16.0 | tomcat11 | 11.0.21-160000.1.1 | openSUSE-SU-2026:20595-1 |
| openSUSE | Tumbleweed | tomcat | 9.0.117-1.1 | openSUSE-SU-2026:10547-1 |
| openSUSE | Tumbleweed | tomcat10 | 10.1.54-1.1 | openSUSE-SU-2026:10548-1 |
| openSUSE | Tumbleweed | tomcat11 | 11.0.21-1.1 | openSUSE-SU-2026:10549-1 |
| AlmaLinux | 10 | tomcat9, tomcat9-lib, tomcat9-webapps and 5 more | 1:9.0.117-2.el10_2.alma.1 | ALSA-2026:36790 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Low.
Low impact. A flaw in Apache Tomcat allows the configured cipher preference order to be bypassed. This could lead to a server using a weaker cipher than intended, potentially reducing the security posture of TLS connections. This affects Red Hat Enterprise Linux systems running Apache Tomcat.
Configure Apache Tomcat to explicitly allow only strong cipher suites. This ensures that even if the preference order is not strictly honored, only secure ciphers are utilized for TLS connections.
Edit the `server.xml` file, typically located at `/etc/tomcat/server.xml` or `/opt/tomcat/conf/server.xml`, and modify the `<Connector>` element to include a `ciphers` attribute listing only approved strong cipher suites. For example:
`<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLSv1.2+TLSv1.3" ciphers="TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_GCM_SHA256"/>`
Replace the example cipher list with a comprehensive set of strong ciphers appropriate for your environment. This may impact compatibility with older clients that do not support the specified strong cipher suites.
A restart of the Apache Tomcat service is required for the changes to take effect. Use the command `systemctl restart tomcat` or `systemctl restart tomcat9` depending on your installed package.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | tomcat | Not affected | |
| Red Hat Enterprise Linux 10 | tomcat9 | Not affected | |
| Red Hat Enterprise Linux 6 | tomcat6 | Not affected | |
| Red Hat Enterprise Linux 7 | tomcat | Not affected | |
| Red Hat Enterprise Linux 8 | pki-deps:10.6/pki-servlet-engine | Not affected | |
| Red Hat Enterprise Linux 8 | tomcat | Not affected | |
| Red Hat Enterprise Linux 9 | pki-servlet-engine | Not affected | |
| Red Hat Enterprise Linux 9 | tomcat | Not affected | |
| Red Hat JBoss Web Server 5 | tomcat | Not affected | |
| Red Hat JBoss Web Server 6 | tomcat | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-29129.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.