Critical Authentication

CVE-2026-29145 — Apache Tomcat, Apache Tomcat Native: OCSP checks sometimes soft-fail even when soft-fail is disabled

CLIENT_CERT authentication does not fail as expected for some scenarios when soft fail is disabled vulnerability in Apache Tomcat, Apache Tomcat Native. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.18, from 10.1.0-M7 through 10.1.52, from 9.0.83 through 9.0.115; Apache Tomcat Native: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39, from 1.3.0 through 1.3.6, from 2.0.0 through 2.0.13. Users are recommended to upgrade to version Tomcat Native 1.3.7 or 2.0.14 and Tomcat 11.0.20, 10.1.53 and 9.0.116, which fix the issue.

Published Apr 9, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: apache

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (critical)+10
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.72%

ahead of 53% of scored CVEs · Oct 14, 2026

Affects

Apache Software Foundation

Tomcat and 1 more

CVSS base

9.1

Critical · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Tomcat, Apache Software Foundation Tomcat Native).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Apache Software Foundation	Tomcat	≥ 10.1.1 and < 10.1.53version 10.1.0-milestone9version 10.1.0-milestone8version 10.1.0-milestone7version 10.1.0-milestone20version 10.1.0-milestone19version 10.1.0-milestone18version 10.1.0-milestone17 and 10 more version 10.1.0-milestone16version 10.1.0-milestone15version 10.1.0-milestone14version 10.1.0-milestone13version 10.1.0-milestone12version 10.1.0-milestone11version 10.1.0-milestone10version 10.1.0≥ 11.0.0 and < 11.0.20≥ 9.0.83 and < 9.0.116	Vulnerable	NIST National Vulnerability Database
Apache Software Foundation	Tomcat	≥ 9.0.83 and ≤ 9.0.115≥ 10.1.0-M7 and ≤ 10.1.52≥ 11.0.0-M1 and ≤ 11.0.18	Vulnerable	CVE Program (cve.org) e CISA ADP
Apache Software Foundation	Tomcat Native	≥ 1.1.23 and < 1.3.7≥ 2.0.0 and < 2.0.14	Vulnerable	NIST National Vulnerability Database
Apache Software Foundation	Tomcat Native	≥ 1.1.23 and ≤ 1.1.34≥ 1.2.0 and ≤ 1.2.39≥ 1.3.0 and ≤ 1.3.6≥ 2.0.0 and ≤ 2.0.13	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.1	CVSS 3.1	Critical	3.9	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.1	CVSS 3.1	Critical	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-287 · Improper Authentication

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.72%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.

web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · apache software foundation/apache tomcat, apache software foundation/apache tomcat native
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 9.1
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Apr 9, 2026 · apache

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

lists.apache.org/thread/yz5fxmhd2j43wgqykssdo7kltws57jfz
Mailing List, Vendor Advisory, vendor-advisory, NIST National Vulnerability Database
www.openwall.com/lists/oss-security/2026/04/09/23
Mailing List, Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor

Authentication
same class

CWE-287
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-86247 Apache Tomcat Native: Client certificate requirements can be down-graded 22d
Critical CVE-2026-86246 Apache Tomcat Native: Insecure OpenSSL options enabled 22d
High CVE-2026-86243 Apache Tomcat Native: DoS via TLS handshake 22d
Critical CVE-2026-55276 Apache Tomcat: Logged effective web.xml is incomplete Jun 29, 2026
Medium CVE-2026-55955 Apache Tomcat: EncryptInterceptor not protected against replay attacks Jun 29, 2026
High CVE-2026-55957 Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind Jun 29, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-29145 is "Apache Tomcat, Apache Tomcat Native: OCSP checks sometimes soft-fail even when soft-fail is disabled", rated Critical. It affects Tomcat (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.72% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.