# CVE-2026-80353: Time-of-check time-of-use (TOCTOU) race condition vulnerability in Apache Tomcat when creating unix domain sockets for the APR/Native connec


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** BIT-tomcat-2026-80353, DEBIAN-CVE-2026-80353, GHSA-wv4g-r8pf-3wmw, UBUNTU-CVE-2026-80353

## What is CVE-2026-80353?

CVE-2026-80353 is a high-severity vulnerability in Apache Tomcat, published on 20 Oct 2026. 

### Official description

Time-of-check time-of-use (TOCTOU) race condition vulnerability in Apache Tomcat when creating unix domain sockets for the APR/Native connector allows an unauthorised local user to access the unix domain socket. The fix for CVE-2026-65183 only addressed the NIO connector. It did not address the same issue in the APR/Native connector.

This issue affects Apache Tomcat: from 9.0.47 through 9.0.122.

Users are recommended to upgrade to version 9.0.123, which fixes the issue.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-80353?

1 open source package ship an affected version, including tomcat.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tomcat` | Bitnami | From 9.0.47 | 9.0.123 |

## How do I fix CVE-2026-80353?

Upgrade tomcat to 9.0.123 or later.

## Is CVE-2026-80353 being exploited?

There is no known exploitation of CVE-2026-80353 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80353 and fix it if it is affected.

What it is: CVE-2026-80353 is a high-severity vulnerability in Apache Tomcat, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-80353 in the wild and no public exploit code.

Affected packages and fixed versions:
- tomcat (Bitnami): affected from 9.0.47; fixed in 9.0.123

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80353/ (Markdown: https://insights.sbomify.com/CVE-2026-80353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80353
- OSV: https://osv.dev/vulnerability/CVE-2026-80353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80353/
Summaries are generated and may contain mistakes; the official description above is the record.