How severe is GHSA-6j88-6whg-x687?

GHSA-6j88-6whg-x687 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6j88-6whg-x687?

GHSA-6j88-6whg-x687 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6j88-6whg-x687?

Update org.apache.tomcat:tomcat to 10.1.0-M17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j88-6whg-x687 is resolved across your whole dependency graph.

How do I detect GHSA-6j88-6whg-x687 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. 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-6j88-6whg-x687 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-6j88-6whg-x687?

O3 pinpoints whether GHSA-6j88-6whg-x687 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-6j88-6whg-x687 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-6j88-6whg-x687, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-6j88-6whg-x687?

GHSA-6j88-6whg-x687 has an EPSS (Exploit Prediction Scoring System) score of 6.2%, placing it in the 93th 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-6j88-6whg-x687?

GHSA-6j88-6whg-x687 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-6j88-6whg-x687?

A Nuclei detection template exists for GHSA-6j88-6whg-x687, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-6j88-6whg-x687 published, and has it been updated?

GHSA-6j88-6whg-x687 was published on June 24, 2022 and was last updated on February 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-6j88-6whg-x687

MEDIUM

Cross-site Scripting in Apache Tomcat

Also known asBIT-tomcat-2022-34305CVE-2022-34305

Published

Jun 24, 2022

Updated

Feb 21, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

6.2%probability of exploitation in next 30 days

Lower Risk93th percentile-11.21%

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

4 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 to 9.0.64 and 8.5.50 to 8.5.81 the Form authentication example in the examples web application displayed user provided data without filtering, exposing a XSS vulnerability.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.1.0-M1&&< 10.1.0-M17	10.1.0-M17
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.0.0-M1&&< 10.0.22	10.0.22
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.30&&< 9.0.65	9.0.65
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.50&&< 8.5.82	8.5.82

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 t…

github.comGithubJun 2022

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. 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 to 10.1.0-M17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j88-6whg-x687 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-6j88-6whg-x687 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-6j88-6whg-x687. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6j88-6whg-x687 in your dependencies?

O3 detects GHSA-6j88-6whg-x687 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