# Apache Tomcat is vulnerable to resource exhaustion when using the APR/Native connector

Advisory record · `GHSA-4j3c-42xv-3f84`

- **Identifiers:** `GHSA-4j3c-42xv-3f84` · `BIT-tomcat-2025-52434` · `CVE-2025-52434`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-362](https://cwe.mitre.org/data/definitions/362.html)
- **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md)
- **Published:** 10 Jul 2025
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Jul 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.tomcat:tomcat-coyote` (Maven): affected `>=9.0.0.M1, <9.0.107 || >=8.5.0, <=8.5.100`; fixed in `9.0.107`
- `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=9.0.0.M1, <9.0.107 || >=8.5.0, <=8.5.100`; fixed in `9.0.107`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Tomcat's APR/Native connector (tomcat-coyote, tomcat-embed-core) is affected from 9.0.0.M1 through 9.0.106 and 8.5.0 through 8.5.100. A race condition, most noticeable when clients close HTTP/2 connections, can cause resource exhaustion. Upgrade to 9.0.107, which fixes the issue.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 81st percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4j3c-42xv-3f84)

## Sources

- [GitHub Advisory Database: GHSA-4j3c-42xv-3f84](https://github.com/advisories/GHSA-4j3c-42xv-3f84)
- [OSV: GHSA-4j3c-42xv-3f84](https://osv.dev/vulnerability/GHSA-4j3c-42xv-3f84)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-52434>
- <https://github.com/apache/tomcat/commit/8a83c3c42d20762782678932c14005cd3397a018>
- <https://github.com/apache/tomcat>
- <https://lists.apache.org/thread/gxgh65004f25y8519coth6w7vchww030>
- <https://lists.debian.org/debian-lts-announce/2025/07/msg00009.html>
- <http://www.openwall.com/lists/oss-security/2025/07/10/11>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4j3c-42xv-3f84>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4j3c-42xv-3f84/>. Everything for agents: <https://agentprime.io/llms.txt>.