Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-34500

Apache Tomcat: Apache Tomcat: Authentication bypass via client certificate misconfiguration

Overview

Published
9 Apr 2026
Modified
26 Oct 2026
Medium CVE
7 Registry packages
77 OS packages
12 Linux distributions
Yes Fix available

Description

CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled and FFM is used in Apache Tomcat.

This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.20, from 10.1.22 through 10.1.53, from 9.0.92 through 9.0.116.

Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117, which fixes the issue.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Weakness: CWE-287

Affected packages · 7

Packages affected by CVE-2026-34500
EcosystemPackageVulnerableFixed in
Bitnami tomcat >=9.0.92, <9.0.117>=10.1.22, <10.1.54>=11.0.0, <11.0.21 9.0.11710.1.5411.0.21
Maven org.apache.tomcat:tomcat-coyote-ffm >=9.0.92, <9.0.117>=10.1.22, <10.1.54>=11.0.0-M14, <11.0.21 9.0.11710.1.5411.0.21
Seal Maven org.apache.tomcat.embed:tomcat-embed-core >=10.1.26+sp0, <10.1.26+sp999>=10.1.28+sp0, <10.1.28+sp999>=10.1.30+sp0, <10.1.30+sp999>=10.1.31+sp0, <10.1.31+sp999>=10.1.34+sp0, <10.1.34+sp999+7 more 10.1.26+sp99910.1.28+sp99910.1.30+sp99910.1.31+sp99910.1.34+sp999
Seal Maven seal.sp1.org.apache.tomcat.embed:tomcat-embed-core >=10.1.26, <10.1.26+sp999>=10.1.28, <10.1.28+sp999>=10.1.30, <10.1.30+sp999>=10.1.31, <10.1.31+sp999>=10.1.34, <10.1.34+sp999+6 more 10.1.26+sp99910.1.28+sp99910.1.30+sp99910.1.31+sp99910.1.34+sp999
Seal Maven seal.sp2.org.apache.tomcat.embed:tomcat-embed-core >=10.1.26, <10.1.26+sp999>=10.1.28, <10.1.28+sp999>=10.1.30, <10.1.30+sp999>=10.1.31, <10.1.31+sp999>=10.1.34, <10.1.34+sp999+3 more 10.1.26+sp99910.1.28+sp99910.1.30+sp99910.1.31+sp99910.1.34+sp999
Seal Maven seal.sp3.org.apache.tomcat.embed:tomcat-embed-core >=10.1.28, <10.1.28+sp999>=10.1.34, <10.1.34+sp999>=10.1.39, <10.1.39+sp999>=10.1.40, <10.1.40+sp999>=9.0.110, <9.0.110+sp999 10.1.28+sp99910.1.34+sp99910.1.39+sp99910.1.40+sp9999.0.110+sp999
Seal Maven seal.sp4.org.apache.tomcat.embed:tomcat-embed-core >=9.0.110, <9.0.110+sp999 9.0.110+sp999

Open a package to see all its vulnerabilities.

Operating systems · 64 fixes

Red Hat 3 releases · 3 packages

affected 1 eol 3 fixed 3
tomcat jws5-tomcat jws6-tomcat
Red Hat fixes for CVE-2026-34500
ReleasePackageFixed inAdvisory
7 tomcat affected —
7 jws5-tomcat eol —
8 jws5-tomcat eol —
8 jws6-tomcat +9 0:10.1.49-13.redhat_00011.1.el8jws RHSA-2026:20405
9 jws5-tomcat eol —
9 jws6-tomcat +9 0:10.1.49-13.redhat_00011.1.el9jws RHSA-2026:20405

1 more row

SUSE Linux Enterprise 6 releases · 3 packages

fixed 13
tomcat tomcat10 tomcat11
SUSE Linux Enterprise fixes for CVE-2026-34500
ReleasePackageFixed inAdvisory
12.5 tomcat +8 9.0.117-3.163.2 SUSE-SU-2026:1572-1
15.4 tomcat +6 9.0.117-150200.105.1 SUSE-SU-2026:1604-1
15.5 tomcat10 +6 10.1.54-150200.5.64.1 SUSE-SU-2026:1603-1
15.5 tomcat +6 9.0.117-150200.105.1 SUSE-SU-2026:1604-1
15.6 tomcat10 +6 10.1.54-150200.5.64.1 SUSE-SU-2026:1603-1
15.6 tomcat11 +6 11.0.21-150600.13.18.1 SUSE-SU-2026:1558-1

7 more rows

alma 2 releases · 2 packages

fixed 2
tomcat9 tomcat
alma fixes for CVE-2026-34500
ReleasePackageFixed in
10 tomcat9 +7 1:9.0.117-2.el10_2.alma.1
9 tomcat +7 1:9.0.117-1.el9_8

amazon linux 1 release · 2 packages

fixed 2
tomcat10 tomcat9
amazon linux fixes for CVE-2026-34500
ReleasePackageFixed in
2023 tomcat10 +7 1:10.1.54-1.amzn2023.0.1
2023 tomcat9 +7 1:9.0.117-1.amzn2023.0.1

chainguard 1 release · 18 packages

fixed 18
kayenta-2025-0 kayenta-fips-2025-0 kayenta-fips-2025-1 kayenta-2025-1 kayenta-2025-2 kayenta-fips-2025-2 +12
chainguard fixes for CVE-2026-34500
ReleasePackageFixed in
kayenta-2025-0 2025.0.8-r11
kayenta-fips-2025-0 2025.0.8-r13
kayenta-fips-2025-1 2025.1.6-r10
kayenta-2025-1 2025.1.6-r9
kayenta-2025-2 2025.2.4-r5
kayenta-fips-2025-2 2025.2.4-r6

12 more rows

debian 4 releases · 3 packages

fixed 9
tomcat9 tomcat10 tomcat11
debian fixes for CVE-2026-34500
ReleasePackageFixed in
11 tomcat9 9.0.118-0+deb11u1
12 tomcat10 10.1.55-1~deb12u1
12 tomcat9 9.0.70-2
13 tomcat10 10.1.55-1~deb13u1
13 tomcat11 11.0.22-1~deb13u1
13 tomcat9 9.0.70-2

3 more rows

echo 1 release · 3 packages

fixed 3
tomcat10 tomcat11 tomcat9
echo fixes for CVE-2026-34500
ReleasePackageFixed in
tomcat10 10.1.55-1~deb12u1
tomcat11 11.0.22-1~deb13u1
tomcat9 9.0.70-2

openSUSE 1 release · 3 packages

fixed 3
tomcat10 tomcat11 tomcat
openSUSE fixes for CVE-2026-34500
ReleasePackageFixed inAdvisory
Tumbleweed tomcat10 +10 10.1.54-1.1 openSUSE-SU-2026:10548-1
Tumbleweed tomcat11 +10 11.0.21-1.1 openSUSE-SU-2026:10549-1
Tumbleweed tomcat +10 9.0.117-1.1 openSUSE-SU-2026:10547-1

openSUSE Leap 1 release · 3 packages

fixed 3
tomcat10 tomcat11 tomcat
openSUSE Leap fixes for CVE-2026-34500
ReleasePackageFixed inAdvisory
16.0 tomcat10 +10 10.1.54-160000.1.1 openSUSE-SU-2026:20612-1
16.0 tomcat11 +10 11.0.21-160000.1.1 openSUSE-SU-2026:20595-1
16.0 tomcat +10 9.0.117-160000.1.1 openSUSE-SU-2026:20611-1

rocky 1 release · 1 package

fixed 2
tomcat9
rocky fixes for CVE-2026-34500
ReleasePackageFixed in
10 tomcat9 +7 1:9.0.117-1.el10_2
10 tomcat9 +7 1:9.0.117-2.el10_2

ubuntu 1 release · 1 package

affected 1
tomcat11
ubuntu fixes for CVE-2026-34500
ReleasePackageFixed in
26.04 tomcat11 affected

wolfi 1 release · 1 package

fixed 1
thingsboard
wolfi fixes for CVE-2026-34500
ReleasePackageFixed in
thingsboard 4.3.1.1-r11

References

Show all 44 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.