Is CVE-2026-68569 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-68569 being exploited in the wild.

How severe is CVE-2026-68569?

High severity, with a CVSS score of 8.1, published 25 August 2026.

Which products and versions are affected?

Apache Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, 8.5.0 through 8.5.100, 7.0.0 through 7.0.109.

Is there a fix for CVE-2026-68569?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-68569 attacked?

It is attacked over the network.

Am I affected by CVE-2026-68569?

Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-68569: Apache Tomcat authentication bypass in DataSourceRealm

CVE-2026-68569 · Severity: high · CVSS 8.1 · Published 2026-08-25

Apache Tomcat is a widely-used application server that handles user authentication for web applications. A flaw in its authentication mechanism allows users to gain access even if they don't actually exist in the system's user database, under specific authentication methods like client certificates or SPNEGO. This creates an unauthorized access risk and could enable attackers to bypass security controls designed to restrict who can use the application.

Technologies: Apache Tomcat. Vendors: Apache.

Quick answers

Is CVE-2026-68569 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-68569 being exploited in the wild.
How severe is CVE-2026-68569?: High severity, with a CVSS score of 8.1, published 25 August 2026.
Which products and versions are affected?: Apache Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, 8.5.0 through 8.5.100, 7.0.0 through 7.0.109.
Is there a fix for CVE-2026-68569?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-68569 attacked?: It is attacked over the network.
Am I affected by CVE-2026-68569?: Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An improper authentication vulnerability in Apache Tomcat's DataSourceRealm component allows a user to be authenticated even when the user does not exist in the realm's database. This occurs specifically when using alternative authentication mechanisms such as CLIENT-CERT or SPNEGO. The vulnerability represents a "fail open" condition where principal lookup fails to properly validate user existence. Affected versions include Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, and older EOL versions 8.5.0 through 8.5.100 and 7.0.0 through 7.0.109. Patches are available in versions 11.0.25, 10.1.58, and 9.0.121.

Affected products

Apache Tomcat 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, 8.5.0 through 8.5.100, 7.0.0 through 7.0.109

Timeline

2026-08-25: disclosed: CVE-2026-68569 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.