MAVEN · AUGUST 2026 · EARLY WARNING

Apache Tomcat Authentication Vulnerability: Critical CVE-2026-68525

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
apache tomcat (maven)
Patched version
11.0.25, 10.1.58, 9.0.121
GHSA-H3X4-894J-XPX5

An Incorrect Authorization vulnerability in Apache Tomcat's FORM authentication process has been identified. Users of affected versions are advised to upgrade immediately.

What happened

Apache Tomcat's FORM authentication process has an Incorrect Authorization vulnerability that allows bypassing security constraints. This vulnerability affects versions from 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 some EOL versions. The issue has been tracked under GHSA-H3X4-894J-XPX5 and CVE-2026-68525. It was first flagged on August 26, 2026.

The vulnerability has not been exploited in the wild as of the latest reports. However, it is classified as a critical CVE and requires immediate attention. Users should consult the primary sources for the most current information and recommendations.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If apache tomcat is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using Apache Tomcat versions from 11.0.0-M1 through 11.0.24, 10.1.0-M1 through 10.1.57, 9.0.0.M1 through 9.0.120, or some EOL versions.

What should I do right now?

Upgrade to version 11.0.25, 10.1.58, or 9.0.121 to fix the issue. Review your deployment configurations and monitor primary sources for updates.

Is this vulnerability being actively exploited?

There are no reports of this vulnerability being exploited in the wild as of the latest information.

Sources

Join the 0Day waitlist →

← Back to all threats