Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2012-5076: Java SE JRE Sandbox Escape

Published Oct 16, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS91.3%100th percentile
CISA KEVYesAdded Mar 28, 2022
In the wildActivePer CISA KEV
Vendors
Oracle CorporationSuse
IdentifiersCVE-2012-5076CWE-20

CVE-2012-5076 is a sandbox-escape vulnerability affecting Oracle Java SE 7 Update 7 and earlier. It allows remote attackers to escape Java sandbox restrictions and execute arbitrary code on the affected machine, compromising confidentiality, integrity, and availability. Component attribution is inconsistent: the vulnerability is described as related to JAX-WS, while another account identifies Java Deployment. The precise root cause and vulnerable function are unspecified. Exploitation was demonstrated against the Java 7u7 browser plug-in and incorporated into the Cool Exploit Kit.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables arbitrary code execution outside the Java sandbox and can compromise the affected machine’s confidentiality, integrity, and availability. The exploit was used by the Cool Exploit Kit, which distributed Reveton ransomware capable of locking victims’ computers and demanding payment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the Java browser plugin and prevent untrusted Java applets from executing in browsers. Restrict or remove Java from systems that do not require it, enforce application allowlisting, and use browser/network controls to block access to exploit-kit landing pages and malicious JAR delivery. Reducing exposure of client-side Java execution is the primary mitigation based on the available information.

Remediation

Patch, then assume compromise.

Upgrade to Java 7 Update 9 or a later supported release incorporating the fix. Oracle addressed CVE-2012-5076 in its October 2012 Critical Patch Update; the demonstrated exploit did not work against Java 7u9.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
java_jre17_glassfish_averagerangestatisticimpl.rbThis repository contains a single Metasploit module targeting CVE-2012-5076, a remote code execution vulnerability in Oracle Java 7u7 and earlier. The exploit abuses the AverageRangeStatisticImpl class in a Java applet to escape the Java sandbox and execute arbitrary code on the victim's machine. The module sets up an HTTP server that serves a malicious HTML page embedding a Java applet, which in turn loads a crafted JAR file containing the exploit and payload classes. The payload can be a Java-based or native (x86) payload for Windows, Linux, or Mac OS X, leveraging Metasploit's payload generation capabilities. The exploit is weaponized, allowing for easy payload customization and delivery via the Metasploit framework. The main attack vector is through a web browser with Java enabled, requiring the victim to visit the attacker's page. The module references several public advisories and is structured according to Metasploit conventions, with clear separation of setup, request handling, and payload delivery logic.Disclosed Oct 16, 2012 · Framework: metasploit · ruby · browserWeaponizedjava_jre17_jaxws.rbThis repository contains a single Metasploit module (modules/exploits/multi/browser/java_jre17_jaxws.rb) that exploits CVE-2012-5076, a remote code execution vulnerability in Oracle Java 7u7 and earlier. The exploit works by serving a malicious Java applet (JAR file) containing specially crafted class files (Exploit.class and MyPayload.class) to a victim's browser. When a user with a vulnerable Java version visits the attacker's web server, the applet is executed outside the Java sandbox, allowing arbitrary code execution. The module supports multiple payloads, including Java and native payloads for Windows and Linux platforms. The exploit is weaponized, as it is part of the Metasploit framework and allows for easy payload customization. The main attack vector is through a web browser, requiring user interaction (visiting a malicious page). The repository structure is typical for a Metasploit module, with the Ruby file implementing the exploit logic and referencing external Java class files as part of the payload delivery.Disclosed Oct 16, 2012 · Framework: metasploit · ruby · browserWeaponized
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationJreapplication
SuseSuse Linux Enterprise Desktopoperating_system
FAQ

Frequently asked questions

Is CVE-2012-5076 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 28, 2022.
Is there a public exploit for CVE-2012-5076?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2012-5076, the earliest disclosed Oct 16, 2012.
Is there a patch for CVE-2012-5076?
Upgrade to Java 7 Update 9 or a later supported release incorporating the fix. Oracle addressed CVE-2012-5076 in its October 2012 Critical Patch Update; the demonstrated exploit did not work against Java 7u9.
What products are affected by CVE-2012-5076?
Oracle Corporation Jre and Suse Linux Enterprise Desktop.
How severe is CVE-2012-5076?
CVE-2012-5076 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 91.3% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware5Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.