How severe is GHSA-mj8x-cpr8-x39h?

No CVSS score has been assigned to GHSA-mj8x-cpr8-x39h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mj8x-cpr8-x39h?

GHSA-mj8x-cpr8-x39h affects the following packages: org.apache.tapestry:tapestry-core (Maven), org.apache.tapestry:tapestry-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mj8x-cpr8-x39h?

Update org.apache.tapestry:tapestry-core to version 5.6.3 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-mj8x-cpr8-x39h actively exploited in the wild?

Yes. There are 9 known exploit references for GHSA-mj8x-cpr8-x39h, including 7 in-the-wild exploitations 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-mj8x-cpr8-x39h?

GHSA-mj8x-cpr8-x39h has an EPSS (Exploit Prediction Scoring System) score of 93.9%, placing it in the 100th 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.

What type of vulnerability is GHSA-mj8x-cpr8-x39h?

GHSA-mj8x-cpr8-x39h is classified as Information Exposure (CWE-200), Deserialization of Untrusted Data (CWE-502). These weakness types 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-mj8x-cpr8-x39h?

A Nuclei detection template exists for GHSA-mj8x-cpr8-x39h, 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-mj8x-cpr8-x39h published, and has it been updated?

GHSA-mj8x-cpr8-x39h was published on June 16, 2021 and was last updated on December 2, 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-mj8x-cpr8-x39h

Remote code execution in Apache Tapestry

Also known asCVE-2021-27850

Published

Jun 16, 2021

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

9 known

EPSS Exploitation Probability

via FIRST.org ↗

93.9%probability of exploitation in next 30 days

Very High Risk100th percentile-0.28%

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

2 pkgs affected

☕org.apache.tapestry:tapestry-core☕org.apache.tapestry:tapestry-core

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

A critical unauthenticated remote code execution vulnerability was found all recent versions of Apache Tapestry. The affected versions include 5.4.5, 5.5.0, 5.6.2 and 5.7.0. The vulnerability I have found is a bypass of the fix for CVE-2019-0195. Recap: Before the fix of CVE-2019-0195 it was possible to download arbitrary class files from the classpath by providing a crafted asset file URL. An attacker was able to download the file AppModule.class by requesting the URL http://localhost:8080/assets/something/services/AppModule.class which contains a HMAC secret key. The fix for that bug was a blacklist filter that checks if the URL ends with .class, .properties or .xml. Bypass: Unfortunately, the blacklist solution can simply be bypassed by appending a / at the end of the URL: http://localhost:8080/assets/something/services/AppModule.class/ The slash is stripped after the blacklist check and the file AppModule.class is loaded into the response. This class usually contains the HMAC secret key which is used to sign serialized Java objects. With the knowledge of that key an attacker can sign a Java gadget chain that leads to RCE (e.g. CommonsBeanUtils1 from ysoserial). Solution for this vulnerability: * For Apache Tapestry 5.4.0 to 5.6.2, upgrade to 5.6.3 or later. * For Apache Tapestry 5.7.0, upgrade to 5.7.1 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tapestry:tapestry-core`	≥ 5.4.0&&< 5.6.3	5.6.3
☕Maven	`org.apache.tapestry:tapestry-core`	≥ 5.7.0&&< 5.7.1	5.7.1

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.