How severe is GHSA-r6j3-px5g-cq3x?

GHSA-r6j3-px5g-cq3x has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r6j3-px5g-cq3x?

GHSA-r6j3-px5g-cq3x affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), and 4 more. Ecosystems affected: Maven.

How do I fix GHSA-r6j3-px5g-cq3x?

Update org.apache.tomcat:tomcat to 11.0.0-M12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6j3-px5g-cq3x is resolved across your whole dependency graph.

How do I detect GHSA-r6j3-px5g-cq3x 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-r6j3-px5g-cq3x 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-r6j3-px5g-cq3x?

O3 pinpoints whether GHSA-r6j3-px5g-cq3x 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-r6j3-px5g-cq3x actively exploited in the wild?

No public exploit code has been indexed for GHSA-r6j3-px5g-cq3x 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-r6j3-px5g-cq3x?

GHSA-r6j3-px5g-cq3x has an EPSS (Exploit Prediction Scoring System) score of 5.8%, placing it in the 92th 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-r6j3-px5g-cq3x?

GHSA-r6j3-px5g-cq3x 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.

Is there exploit tooling available for GHSA-r6j3-px5g-cq3x?

A Nuclei detection template exists for GHSA-r6j3-px5g-cq3x, 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-r6j3-px5g-cq3x published, and has it been updated?

GHSA-r6j3-px5g-cq3x was published on October 10, 2023 and was last updated on June 12, 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

GHSA-r6j3-px5g-cq3x

MEDIUM

Apache Tomcat Improper Input Validation vulnerability

Also known asBIT-tomcat-2023-45648CVE-2023-45648

Published

Oct 10, 2023

Updated

Jun 12, 2026

Affected

12 pkgs

Patched

12 / 12

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

5.8%probability of exploitation in next 30 days

Lower Risk92th percentile-56.90%

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

12 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core+4 more

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 from 11.0.0-M1 through 11.0.0-M11, from 10.1.0-M1 through 10.1.13, from 9.0.0-M1 through 9.0.81 and from 8.5.0 through 8.5.93 did not correctly parse HTTP trailer headers. A specially crafted, invalid trailer header could cause Tomcat to treat a single request as multiple requests leading to the possibility of request smuggling when behind a reverse proxy. Older, EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.0-M12 onwards, 10.1.14 onwards, 9.0.81 onwards or 8.5.94 onwards, which fix the issue.

Affected Packages

12 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 11.0.0-M1&&< 11.0.0-M12	11.0.0-M12
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.1.0-M1&&< 10.1.14	10.1.14
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0-M1&&< 9.0.81	9.0.81
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.0&&< 8.5.94	8.5.94
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 11.0.0-M1&&< 11.0.0-M12	11.0.0-M12
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 10.1.0-M1&&< 10.1.14	10.1.14

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

Frequently Asked Questions

Improper Input Validation vulnerability in Apache Tomcat. Tomcat from 11.0.0-M1 through 11.0.0-M11, from 10.1.0-M1 through 10.1.13, from 9.0.0-M1 through 9.0.81 and from 8.5.0 through 8.5.93 did not correctly parse HTTP trailer headers. A specially crafted, invalid trailer header could cause Tomcat to treat a single request as multiple requests leading to the possibility of request smuggling when behind a reverse proxy. Older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0-M12 onwards, 10.1.14 onwards, 9.0.81 onwards or 8.5.94 onwards, which fix the is

O3 Security · Impact-Aware SCA

Is GHSA-r6j3-px5g-cq3x in your dependencies?

O3 detects GHSA-r6j3-px5g-cq3x 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