# CVE-2012-4681: Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution

> Remote attackers can execute arbitrary code by bypassing Java SecurityManager restrictions via crafted applets, affecting Java Runtime Environment users.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2012
- **Updated:** 6 Aug 2026
- **Also known as:** CVE-2012-3539, GHSA-fw99-8m5g-58p8

## What is CVE-2012-4681?

CVE-2012-4681 is a critical vulnerability in Oracle Jdk, published on 28 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple vulnerabilities in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 6 and earlier allow remote attackers to execute arbitrary code via a crafted applet that bypasses SecurityManager restrictions by (1) using com.sun.beans.finder.ClassFinder.findClass and leveraging an exception with the forName method to access restricted classes from arbitrary packages such as sun.awt.SunToolkit, then (2) using "reflection with a trusted immediate caller" to leverage the getField method to access and modify private fields, as exploited in the wild in August 2012 using Gondzz.class and Gondvv.class.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2012-4681?

It affects 6 products.


Products: Oracle Jdk, Oracle Jre, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2012-4681?

Upgrade to a fixed version. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2012-4681 being exploited?

Yes. Attackers have exploited CVE-2012-4681 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Public exploit code:

- An A/V evasion armoring experiment for CVE-2012-4681 (github_poc): https://github.com/benjholla/CVE-2012-4681-Armoring
- Java 7 Applet Remote Code Execution (metasploit)
- Java 7 Applet - Remote Code Execution (Metasploit) (exploitdb)
- A Simple PoC for CVE-2012-4681 (github_poc): https://github.com/ZH3FENG/PoCs-CVE_2012_4681

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)
- [CVE-2015-4844](https://insights.sbomify.com/CVE-2015-4844/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4681 and fix it if it is affected.

What it is: CVE-2012-4681 is a critical vulnerability in Oracle Jdk, published on 28 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2012-4681 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Affected product: Oracle Jdk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-4681/ (Markdown: https://insights.sbomify.com/CVE-2012-4681/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4681
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4681
- OSV: https://osv.dev/vulnerability/CVE-2012-4681

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-4681/
Summaries are generated and may contain mistakes; the official description above is the record.