PatchSiren cyber security CVE debrief
CVE-2026-68569 Apache CVE debrief
CVE-2026-68569 Improper Authentication vulnerability in Apache Tomcat allows authentication of non-existent users in certain circumstances. Affected versions include 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, and 7.0.0 through 7.0.109. Users should upgrade to version 11.0.25, 10.1.58, or 9.0.121.
- Vendor
- Apache
- Product
- Tomcat
- CVSS
- HIGH 8.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-25
- Original CVE updated
- 2026-09-21
- Advisory published
- 2026-08-25
- Advisory updated
- 2026-09-21
Who should care
Administrators and security teams responsible for Apache Tomcat deployments should assess exposure and upgrade to fixed versions to prevent improper authentication. They should verify authentication configurations to prevent unauthorized access and review affected versions to ensure secure authentication.
Why it matters
CVE-2026-68569 Improper Authentication vulnerability in Apache Tomcat allows authentication of non-existent users in certain circumstances, requiring verification and upgrade to fixed versions.
- Verify authentication configurations to prevent unauthorized access
- Upgrade to fixed versions to prevent improper authentication
- Review and update affected versions to ensure secure authentication
Technical summary
The Improper Authentication vulnerability in Apache Tomcat allows a user to be authenticated even if the user does not exist in the DataSourceRealm in certain circumstances, such as CLIENT-CERT and SPNEGO. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other unsupported versions may also be affected.
Defensive priority
Upgrade to fixed versions to prevent improper authentication
Recommended defensive actions
- Upgrade Apache Tomcat to version 11.0.25, 10.1.58, or 9.0.121
- Review and update affected versions 8.5.0 through 8.5.100 and 7.0.0 through 7.0.109
- Verify authentication configurations for CLIENT-CERT and SPNEGO
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability and affected versions. The Improper Authentication vulnerability in Apache Tomcat allows a user to be authenticated even if the user does not exist in the DataSourceRealm in certain circumstances, such as CLIENT-CERT and SPNEGO. Affected versions include 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, and 7.0.0 through 7.0.109. Users should verify authentication configurations to prevent unauthorized access and are
Sources and references
Verified primary and authoritative sources
-
CVE-2026-68569 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-68569
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-68569 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-68569
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://lists.apache.org/thread/8robqo76q0osxgw0b5lcwgz0hcf9h4zc
[email protected] - Mailing List, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.