cve.bz

CVE-2026-29129 apache tomcat

7.5 highEPSS 0.3%Fix available

High (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.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-29129

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-29129](https://cve.bz/cve/badge/CVE-2026-29129.svg)](https://cve.bz/cve/CVE-2026-29129)

HTML:

<a href="https://cve.bz/cve/CVE-2026-29129"><img src="https://cve.bz/cve/badge/CVE-2026-29129.svg" alt="CVE-2026-29129"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Tomcatfrom 11.0.16 through 11.0.18
Apache Software Foundation Apache Tomcatfrom 10.1.51 through 10.1.52
Apache Software Foundation Apache Tomcatfrom 9.0.114 through 9.0.115

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat-coyote>=9.0.114 <9.0.1169.0.116
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat-coyote>=10.1.51 <10.1.5310.1.53
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat-coyote>=11.0.16 <11.0.2011.0.20
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat>=9.0.114 <9.0.1169.0.116
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat>=10.1.51 <10.1.5310.1.53
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat:tomcat>=11.0.16 <11.0.2011.0.20
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat.embed:tomcat-embed-core>=9.0.114 <9.0.1169.0.116
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat.embed:tomcat-embed-core>=10.1.51 <10.1.5310.1.53
GHSA-69cc-cv78-qc8gMavenorg.apache.tomcat.embed:tomcat-embed-core>=11.0.16 <11.0.2011.0.20

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12tomcat1010.1.55-1~deb12u1DEBIAN-CVE-2026-29129
Debian12, 13, 14tomcat99.0.70-2DEBIAN-CVE-2026-29129
Debian13tomcat1010.1.55-1~deb13u1DEBIAN-CVE-2026-29129
Debian13tomcat1111.0.22-1~deb13u1DEBIAN-CVE-2026-29129
Debian14tomcat1010.1.54-1DEBIAN-CVE-2026-29129
Debian14tomcat1111.0.21-1DEBIAN-CVE-2026-29129
Ubuntu26.04:LTStomcat11no fix listedUBUNTU-CVE-2026-29129
SUSELinux 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 moretomcat9.0.117-150200.105.1SUSE-SU-2026:1604-1
SUSELinux 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 moretomcat1010.1.54-150200.5.64.1SUSE-SU-2026:1603-1
SUSELinux Enterprise Module for Web and Scripting 15 SP7, Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6tomcat1111.0.21-150600.13.18.1SUSE-SU-2026:1558-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5tomcat9.0.117-3.163.2SUSE-SU-2026:1572-1
openSUSELeap 16.0tomcat9.0.117-160000.1.1openSUSE-SU-2026:20611-1
openSUSELeap 16.0tomcat1010.1.54-160000.1.1openSUSE-SU-2026:20612-1
openSUSELeap 16.0tomcat1111.0.21-160000.1.1openSUSE-SU-2026:20595-1
openSUSETumbleweedtomcat9.0.117-1.1openSUSE-SU-2026:10547-1
openSUSETumbleweedtomcat1010.1.54-1.1openSUSE-SU-2026:10548-1
openSUSETumbleweedtomcat1111.0.21-1.1openSUSE-SU-2026:10549-1
AlmaLinux10tomcat9, tomcat9-lib, tomcat9-webapps and 5 more1:9.0.117-2.el10_2.alma.1ALSA-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

Red Hat rates this Low.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10tomcatNot affected
Red Hat Enterprise Linux 10tomcat9Not affected
Red Hat Enterprise Linux 6tomcat6Not affected
Red Hat Enterprise Linux 7tomcatNot affected
Red Hat Enterprise Linux 8pki-deps:10.6/pki-servlet-engineNot affected
Red Hat Enterprise Linux 8tomcatNot affected
Red Hat Enterprise Linux 9pki-servlet-engineNot affected
Red Hat Enterprise Linux 9tomcatNot affected
Red Hat JBoss Web Server 5tomcatNot affected
Red Hat JBoss Web Server 6tomcatNot 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.

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON