cve.bz

CVE-2026-55957 apache tomcat: Missing Critical Step in Authentication

7.3 highEPSS 2.9%Fix available

High (7.3) in apache tomcat. EPSS 2.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.tomcat.embed:tomcat-embed-core 10.1.37, 11.0.5, 9.0.101.

On this page
Missing Critical Step in Authentication vulnerability in Apache Tomcat when the JNDIRealm was configured to authenticate binds using GSSAPI allowed attackers to authenticate without provided the correct password. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.4, from 10.1.0-M1 through 10.1.36, from 9.0.0.M1 through 9.0.100, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Users are recommended to upgrade to version 11.0.5, 10.1.37 or 9.0.101, which fixes the issue.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
2.9% (unchanged from 2.9% a week ago; 2.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th 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: total, assessed 2026-06-30. 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-304 Missing Critical Step in Authentication
OWASP Top 10
A07:2025 Authentication 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-55957 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55957?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55957?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-55957 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-55957

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-55957](https://cve.bz/cve/badge/CVE-2026-55957.svg)](https://cve.bz/cve/CVE-2026-55957)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Tomcatfrom 11.0.0-M1 through 11.0.4
Apache Software Foundation Apache Tomcatfrom 10.1.0-M1 through 10.1.36
Apache Software Foundation Apache Tomcatfrom 9.0.0.M1 through 9.0.100
Apache Software Foundation Apache Tomcatfrom 8.5.0 through 8.5.100
Apache Software Foundation Apache Tomcatfrom 7.0.0 through 7.0.109

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat.embed:tomcat-embed-core>=11.0.0-M1 <11.0.511.0.5
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1 <10.1.3710.1.37
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat.embed:tomcat-embed-core>=9.0.0.M1 <9.0.1019.0.101
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat.embed:tomcat-embed-core>=8.5.0 <=8.5.100no fix published
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat.embed:tomcat-embed-core<=7.0.109no fix published
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat>=11.0.0-M1 <11.0.511.0.5
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat>=10.1.0-M1 <10.1.3710.1.37
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat>=9.0.0.M1 <9.0.1019.0.101
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat>=8.5.0 <=8.5.100no fix published
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat<=7.0.109no fix published
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat-catalina>=11.0.0-M1 <11.0.511.0.5
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat-catalina>=10.1.0-M1 <10.1.3710.1.37
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat-catalina>=9.0.0.M1 <9.0.1019.0.101
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat-catalina>=8.5.0 <=8.5.100no fix published
GHSA-7895-gffq-w6jqMavenorg.apache.tomcat:tomcat-catalina<=7.0.109no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12tomcat1010.1.52-1~deb12u1DEBIAN-CVE-2026-55957
Debian12, 13, 14tomcat99.0.70-2DEBIAN-CVE-2026-55957
Debian13tomcat1010.1.52-1~deb13u1DEBIAN-CVE-2026-55957
Debian13tomcat1111.0.15-1~deb13u1DEBIAN-CVE-2026-55957
Debian14tomcat1010.1.40-1DEBIAN-CVE-2026-55957
Debian14tomcat1111.0.5-1DEBIAN-CVE-2026-55957
Ubuntu24.04:LTStomcat9, tomcat10no fix listedUBUNTU-CVE-2026-55957
Ubuntu25.10, 26.04:LTS, 26.10tomcat9, tomcat10, tomcat11no fix listedUBUNTU-CVE-2026-55957
UbuntuPro:14.04:LTStomcat6, tomcat7no fix listedUBUNTU-CVE-2026-55957
UbuntuPro:16.04:LTStomcat7, tomcat8no fix listedUBUNTU-CVE-2026-55957
UbuntuPro:18.04:LTStomcat8, tomcat9no fix listedUBUNTU-CVE-2026-55957
UbuntuPro:20.04:LTS, Pro:22.04:LTStomcat9no fix listedUBUNTU-CVE-2026-55957
Red Hatenterprise_linux:8::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el8_10RHSA-2026:68677
Red Hatenterprise_linux:9::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.110-2.el9_8RHSA-2026:18916
Red Hatenterprise_linux:10.2tomcat, tomcat-lib, tomcat-webapps and 5 more1:10.1.49-1.el10RHSA-2026:18537
Red Hatenterprise_linux:10.2tomcat9, tomcat9-lib, tomcat9-webapps and 5 more1:9.0.110-2.el10_2RHSA-2026:18536
Red Hatenterprise_linux_eus:10.0tomcat, tomcat-lib, tomcat-webapps and 5 more1:10.1.49-1.el10_0RHSA-2026:67164
Red Hatenterprise_linux_eus:10.0tomcat9, tomcat9-lib, tomcat9-webapps and 5 more1:9.0.120-1.el10_0RHSA-2026:67163
Red Hathummingbird:1tomcat10, tomcat10-lib, tomcat10-common and 7 more1:10.1.56-1.hum1RHSA-2026:29203
Red Hathummingbird:1tomcat11, tomcat11-lib, tomcat11-common and 7 more1:11.0.23-0.1.hum1RHSA-2026:32960
Red Hatrhel_e4s:8.8::appstream, rhel_tus:8.8::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el8_8RHSA-2026:68680
Red Hatrhel_e4s:9.2::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el9_2RHSA-2026:68678
Red Hatrhel_e4s:9.4::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el9_4RHSA-2026:68679
Red Hatrhel_eus:9.6::appstreamtomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el9_6RHSA-2026:68659
AlmaLinux8tomcat, tomcat-lib, tomcat-webapps and 5 more1:9.0.120-1.el8_10ALSA-2026:68677
Rocky Linux8tomcat1:9.0.120-1.el8_10RLSA-2026:68677

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This issue is rated as Important severity because it allows an attacker to fully bypass password verification when authenticating against a Tomcat instance, potentially gaining unauthorized access to protected resources without any privileges or user interaction required.

Red Hat's mitigation

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10tomcat9-1:9.0.110-2.el10_2Fixed 2026-05-19RHSA-2026:18536
Red Hat Enterprise Linux 10tomcat-1:10.1.49-1.el10Fixed 2026-05-19RHSA-2026:18537
Red Hat Enterprise Linux 10.0 Extended Update Supporttomcat9-1:9.0.120-1.el10_0Fixed 2026-09-14RHSA-2026:67163
Red Hat Enterprise Linux 10.0 Extended Update Supporttomcat-1:10.1.49-1.el10_0Fixed 2026-09-14RHSA-2026:67164
Red Hat Enterprise Linux 8tomcat-1:9.0.120-1.el8_10Fixed 2026-09-17RHSA-2026:68677
Red Hat Enterprise Linux 8.8 Telecommunications Update Servicetomcat-1:9.0.120-1.el8_8Fixed 2026-09-17RHSA-2026:68680
Red Hat Enterprise Linux 8.8 Update Services for SAP Solutionstomcat-1:9.0.120-1.el8_8Fixed 2026-09-17RHSA-2026:68680
Red Hat Enterprise Linux 9tomcat-1:9.0.110-2.el9_8Fixed 2026-05-19RHSA-2026:18916
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionstomcat-1:9.0.120-1.el9_2Fixed 2026-09-17RHSA-2026:68678
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutionstomcat-1:9.0.120-1.el9_4Fixed 2026-09-17RHSA-2026:68679
Red Hat Enterprise Linux 9.6 Extended Update Supporttomcat-1:9.0.120-1.el9_6Fixed 2026-09-17RHSA-2026:68659
Red Hat Hardened Imagestomcat10-main-10.1.56-1.hum1Fixed 2026-06-24RHSA-2026:29203
Red Hat Hardened Imagestomcat11-main-11.0.23-0.1.hum1Fixed 2026-06-29RHSA-2026:32960
Red Hat Enterprise Linux 6tomcat6Not affected
Red Hat Enterprise Linux 7tomcatAffected
Red Hat Enterprise Linux 8pki-deps:10.6/pki-servlet-engineNot affected
Red Hat Enterprise Linux 9pki-servlet-engineNot affected
Red Hat JBoss Web Server 5jws5-tomcatWill not fix

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-55957.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • mdvpat/CVE-2026-55957-PoC Harbor Check: matches CVE 0 stars, Java, created
    Reproducible Docker lab for the Apache Tomcat JNDIRealm GSSAPI authentication bypass

References

Check your stackJSON