Skip to content

Apache Tomcat: Configured cipher preference order not preserved

High severity GitHub Reviewed Published Apr 9, 2026 to the GitHub Advisory Database • Updated May 20, 2026

Package

maven org.apache.tomcat.embed:tomcat-embed-core (Maven)

Affected versions

>= 9.0.114, < 9.0.116
>= 10.1.51, < 10.1.53
>= 11.0.16, < 11.0.20

Patched versions

9.0.116
10.1.53
11.0.20
maven org.apache.tomcat:tomcat (Maven)
>= 9.0.114, < 9.0.116
>= 10.1.51, < 10.1.53
>= 11.0.16, < 11.0.20
9.0.116
10.1.53
11.0.20
maven org.apache.tomcat:tomcat-coyote (Maven)
>= 9.0.114, < 9.0.116
>= 10.1.51, < 10.1.53
>= 11.0.16, < 11.0.20
9.0.116
10.1.53
11.0.20

Description

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.

References

Published by the National Vulnerability Database Apr 9, 2026
Published to the GitHub Advisory Database Apr 9, 2026
Reviewed Apr 10, 2026
Last updated May 20, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(10th percentile)

Weaknesses

Use of a Broken or Risky Cryptographic Algorithm

The product uses a broken or risky cryptographic algorithm or protocol. Learn more on MITRE.

CVE ID

CVE-2026-29129

GHSA ID

GHSA-69cc-cv78-qc8g

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.
⚡