How severe is GHSA-qq5r-98hh-rxc9?

No CVSS score has been assigned to GHSA-qq5r-98hh-rxc9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qq5r-98hh-rxc9?

GHSA-qq5r-98hh-rxc9 affects the following packages: org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat:tomcat-coyote (Maven), org.apache.tomcat:tomcat-coyote (Maven). Ecosystems affected: Maven.

How do I fix GHSA-qq5r-98hh-rxc9?

Update org.apache.tomcat:tomcat-coyote to 11.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq5r-98hh-rxc9 is resolved across your whole dependency graph.

How do I detect GHSA-qq5r-98hh-rxc9 in my Maven dependencies?

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.

How do I mitigate GHSA-qq5r-98hh-rxc9 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-qq5r-98hh-rxc9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qq5r-98hh-rxc9 can be triaged on real exposure rather than presence alone.

Is GHSA-qq5r-98hh-rxc9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qq5r-98hh-rxc9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qq5r-98hh-rxc9?

GHSA-qq5r-98hh-rxc9 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qq5r-98hh-rxc9?

GHSA-qq5r-98hh-rxc9 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qq5r-98hh-rxc9 published, and has it been updated?

GHSA-qq5r-98hh-rxc9 was published on February 17, 2026 and was last updated on September 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-qq5r-98hh-rxc9 — tomcat-coyote

Fix: apache/tomcat@2e2fa23

GHSA-qq5r-98hh-rxc9 is a 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 - Security constraint bypass with HTTP/0.9

Also known asBIT-tomcat-2026-24733CVE-2026-24733

Published

Feb 17, 2026

Updated

Sep 11, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-qq5r-98hh-rxc9.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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.

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote

Real-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.

Tomcat did not limit HTTP/0.9 requests to the GET method. If a security constraint was configured to allow HEAD requests to a URI but deny GET requests, the user could bypass that constraint on GET requests by sending a (specification invalid) HEAD request using HTTP/0.9.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0.M1 through 9.0.112.

Older, EOL versions are also affected.

Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fixes the issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 11.0.0-M1&&< 11.0.15	11.0.15`org.apache.tomcat:tomcat-coyote:11.0.15`
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 10.1.0-M1&&< 10.1.50	10.1.50`org.apache.tomcat:tomcat-coyote:10.1.50`
☕Maven	`org.apache.tomcat:tomcat-coyote`	all versions	9.0.113`org.apache.tomcat:tomcat-coyote:9.0.113`

Detection & mitigation playbook

Open-source dependency

Detect
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.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq5r-98hh-rxc9 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-qq5r-98hh-rxc9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qq5r-98hh-rxc9. 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.

Red HatLow

This flaw is only exploitable when Tomcat is configured to allow HEAD requests but deny GET requests to the same resource, a very unlikely configuration. Due to this reason, this flaw has been rated with a low severity.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`tomcat9-1:9.0.117-2.el10_2`	RHSA-2026:36790
Red Hat JBoss Web Server 6.2.2	see advisory	RHSA-2026:12195
Red Hat JBoss Web Server 6.2 on RHEL 10	`jws6-tomcat-0:10.1.49-10.redhat_00008.1.el10jws`	RHSA-2026:12194
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

Improper Input Validation vulnerability in Apache Tomcat. Tomcat did not limit HTTP/0.9 requests to the GET method. If a security constraint was configured to allow HEAD requests to a URI but deny GET requests, the user could bypass that constraint on GET requests by sending a (specification invalid) HEAD request using HTTP/0.9. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0.M1 through 9.0.112. Older, EOL versions are also affected. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or lat

O3 Security · Impact-Aware SCA

Is GHSA-qq5r-98hh-rxc9 in your dependencies?

O3 Security finds GHSA-qq5r-98hh-rxc9 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works