# CVE-2026-65183: Apache Tomcat: TOCTOU when setting specific permissions for Unix Domain Sockets

> A race condition in Apache Tomcat allows local attackers to bypass Unix domain socket permissions, potentially gaining unauthorized access.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BIT-tomcat-2026-65183, DEBIAN-CVE-2026-65183, GHSA-h3mr-2w3q-jcv9, MINI-5wjg-8f22-q277, MINI-65v6-4rj4-2jpm, MINI-prfx-58cw-5582, UBUNTU-CVE-2026-65183

## What is CVE-2026-65183?

CVE-2026-65183 is a high-severity vulnerability in Apache Tomcat, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Apache Tomcat when creating unix domain sockets allows an unauthorised local user to access the unix domain socket.

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.42 through 9.0.120.

Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tomcat` | Bitnami | From 9.0.42 | 9.0.121, 10.1.58, 11.0.25 |

Products: Apache Tomcat.

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

Upgrade tomcat to a fixed version for your release line: 9.0.121, 10.1.58 or 11.0.25.

## Is CVE-2026-65183 being exploited?

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

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65183 is a high-severity vulnerability in Apache Tomcat, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65183 in the wild and no public exploit code.

Affected packages and fixed versions:
- tomcat (Bitnami): affected from 9.0.42; fixed in 9.0.121, 10.1.58, 11.0.25

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-65183/ (Markdown: https://insights.sbomify.com/CVE-2026-65183/index.md)
```

## Sources

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

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