# CVE-2026-80353: Apache Tomcat TOCTOU race condition in APR/Native connector

Source: https://junglewise.ai/threats/cve-2026-80353-time-of-check-time-of-use-toctou-race-condition-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-20. Updated: 2026-10-20  
License: CC BY 4.0 with a link back

CVE-2026-80353 · Severity: info · Published 2026-10-20

Apache Tomcat is a widely used Java application server. A race condition in how it creates Unix domain sockets on Linux systems could allow an unprivileged local user to access the socket and potentially interact with Tomcat. This affects deployments where Tomcat runs on shared systems or in containers with untrusted local users.

Technologies: [Apache Tomcat](https://junglewise.ai/threats/technologies/tomcat). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-80353 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-80353 being exploited in the wild.

**How severe is CVE-2026-80353?** Informational severity, published 20 October 2026.

**Which products and versions are affected?** Apache Tomcat 9.0.47 through 9.0.122.

**Is there a fix for CVE-2026-80353?** Yes: fixed in 9.0.123. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-80353 attacked?** It is attacked with local access, in a web application.

**Am I affected by CVE-2026-80353?** 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.

## How to fix

- Fixed in 9.0.123

## Technical details

A time-of-check time-of-use (TOCTOU) race condition exists in the APR/Native connector's Unix domain socket creation. An unprivileged local attacker can exploit the window between socket creation and permission setting to gain unauthorized access. The vulnerability requires local network access and does not affect the NIO connector, which was addressed in a prior fix (CVE-2026-65183).

## Affected products

- Apache Tomcat 9.0.47 through 9.0.122

## Timeline

- 2026-10-20: disclosed

## References

- [https://lists.apache.org/thread.html/tr0q87qwvs80p9hc53tkwpzvnx0ywftr](https://lists.apache.org/thread.html/tr0q87qwvs80p9hc53tkwpzvnx0ywftr)

## Related threats

- [Apache Tomcat Jakarta Security credential handler bypass](https://junglewise.ai/threats/cve-2026-111248-the-jakarta-security-identity-store-backed-by-the-tomcat-user)
- [Apache Tomcat incomplete cleanup in TLS 1.3 connections](https://junglewise.ai/threats/cve-2026-93446-incomplete-cleanup-vulnerability-in-apache-tomcat-could-cause-tls)
- [Apache Tomcat HTTP trailer information leak between requests](https://junglewise.ai/threats/cve-2026-88041-incomplete-cleanup-vulnerability-in-apache-tomcat-allowed-an)
- [Apache Tomcat Execution After Redirect vulnerability](https://junglewise.ai/threats/cve-2026-74049-execution-after-redirect-ear-vulnerability-in-apache-tomcat-this)
- [Apache Tomcat FIPS mode validation not failing securely](https://junglewise.ai/threats/cve-2026-74048-not-failing-securely-failing-open-vulnerability-in-apache-tomcat)