GHSA-mgp5-rv84-w37q — tomcat-coyote
HIGHGHSA-mgp5-rv84-w37q is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.apache.tomcat:tomcat-coyote. A fix is available for org.apache.tomcat:tomcat-coyote — see the affected versions and patch details below.
Apache Tomcat has an Improper Input Validation vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mgp5-rv84-w37q.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-mgp5-rv84-w37q plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Improper Input Validation vulnerability in Apache Tomcat Native, Apache Tomcat.
When using an OCSP responder, Tomcat Native (and Tomcat's FFM port of the Tomcat Native code) did not complete verification or freshness checks on the OCSP response which could allow certificate revocation to be bypassed.
This issue affects Apache Tomcat Native: from 1.3.0 through 1.3.4, from 2.0.0 through 2.0.11; Apache Tomcat: from 11.0.0-M1 through 11.0.17, from 10.1.0-M7 through 10.1.51, from 9.0.83 through 9.0.114.
The following versions were EOL at the time the CVE was created but are known to be affected: from 1.1.23 through 1.1.34, from 1.2.0 through 1.2.39. Older EOL versions are not affected.
Apache Tomcat Native users are recommended to upgrade to versions 1.3.5 or later or 2.0.12 or later, which fix the issue.
Apache Tomcat users are recommended to upgrade to versions 11.0.18 or later, 10.1.52 or later or 9.0.115 or later which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat-coyote | ≥ 11.0.0-M1&&< 11.0.18 | 11.0.18org.apache.tomcat:tomcat-coyote:11.0.18 |
| ☕Maven | org.apache.tomcat:tomcat-coyote | ≥ 10.1.0-M7&&< 10.1.52 | 10.1.52org.apache.tomcat:tomcat-coyote:10.1.52 |
| ☕Maven | org.apache.tomcat:tomcat-coyote | ≥ 9.0.83&&< 9.0.115 | 9.0.115org.apache.tomcat:tomcat-coyote:9.0.115 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 11.0.0-M1&&< 11.0.18 | 11.0.18org.apache.tomcat.embed:tomcat-embed-core:11.0.18 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 10.1.0-M7&&< 10.1.52 | 10.1.52org.apache.tomcat.embed:tomcat-embed-core:10.1.52 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.83&&< 9.0.115 | 9.0.115org.apache.tomcat.embed:tomcat-embed-core:9.0.115 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-coyote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat-coyote to 11.0.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgp5-rv84-w37q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mgp5-rv84-w37q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mgp5-rv84-w37q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability doesn't affect the Apache Tomcat distributed with Red Hat Enterprise 8 and Red Hat Enterprise up to the version 9.7 as the vulnerable code is not built. The vulnerable code is compiled with Red Hat Enterprise Linux 9.8 and above.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | tomcat-1:10.1.49-1.el10_2.1 | RHSA-2026:19054 |
| Red Hat Enterprise Linux 10 | tomcat9-1:9.0.117-2.el10_2 | RHSA-2026:36790 |
| Red Hat Enterprise Linux 9 | tomcat-1:9.0.117-1.el9_8 | RHSA-2026:26323 |
| Red Hat JBoss Web Server 6.2.1 | tomcat | RHSA-2026:5612 |
| Red Hat JBoss Web Server 6.2 on RHEL 10 | jws6-tomcat-0:10.1.49-9.redhat_00007.1.el10jws | RHSA-2026:5611 |
| Red Hat Hardened Images | tomcat11-main-11.0.21-0.1.hum1 | RHSA-2026:6569 |
| Red Hat Hardened Images | tomcat10-main-10.1.54-1.hum1 | RHSA-2026:8334 |
Frequently Asked Questions
Is GHSA-mgp5-rv84-w37q in your dependencies?
O3 Security finds GHSA-mgp5-rv84-w37q across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.