How severe is GHSA-f268-65qc-98vg?

GHSA-f268-65qc-98vg has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-f268-65qc-98vg?

GHSA-f268-65qc-98vg 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-f268-65qc-98vg?

Update org.apache.tomcat:tomcat-coyote to 10.0.0-M8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f268-65qc-98vg is resolved across your whole dependency graph.

How do I detect GHSA-f268-65qc-98vg 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f268-65qc-98vg 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-f268-65qc-98vg?

O3 pinpoints whether GHSA-f268-65qc-98vg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f268-65qc-98vg actively exploited in the wild?

No public exploit code has been indexed for GHSA-f268-65qc-98vg 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-f268-65qc-98vg?

GHSA-f268-65qc-98vg has an EPSS (Exploit Prediction Scoring System) score of 57.3%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

When was GHSA-f268-65qc-98vg published, and has it been updated?

GHSA-f268-65qc-98vg was published on February 9, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-f268-65qc-98vg: tomcat-coyote (Medium 4.3)

EPSS Exploitation Probability

via FIRST.org ↗

57.3%probability of exploitation in next 30 days

High Risk99th percentile+45.16%

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.

Blast Radius

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

If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 10.0.0-M1&&< 10.0.0-M8	10.0.0-M8
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 9.0.0-M1&&< 9.0.38	9.0.38
☕Maven	`org.apache.tomcat:tomcat-coyote`	≥ 8.5.0&&< 8.5.58	8.5.58

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.tomcat:tomcat-coyote to 10.0.0-M8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f268-65qc-98vg 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 pinpoints whether GHSA-f268-65qc-98vg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f268-65qc-98vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.

O3 Security · Impact-Aware SCA

Is GHSA-f268-65qc-98vg in your dependencies?

O3 detects GHSA-f268-65qc-98vg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-f268-65qc-98vg