How severe is CVE-2013-0431?

CVE-2013-0431 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2013-0431?

CVE-2013-0431 affects the following products: oracle jre, oracle openjdk.

How do I patch CVE-2013-0431?

No patch has shipped for CVE-2013-0431 yet — track the oracle jre advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2013-0431 across my infrastructure?

Inventory every oracle jre deployment and check each version against the affected-products list above.

How do I mitigate CVE-2013-0431 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. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2013-0431 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2013-0431, including 1 documented proof-of-concept exploit on Exploit-DB and 3 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 CVE-2013-0431?

CVE-2013-0431 has an EPSS (Exploit Prediction Scoring System) score of 90.1%, 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.

Is CVE-2013-0431 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2013-0431 (Oracle JRE Sandbox Bypass Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2013-0431?

CVE-2013-0431 is classified as CWE-693 (CWE-693). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2013-0431?

CVE-2013-0431 affects oracle jre (1 version, e.g. 1.7.0); oracle openjdk (1 version, e.g. 7). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2013-0431 published, and has it been updated?

CVE-2013-0431 was published on January 31, 2013 and was last updated on October 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

LOW severity

CVE-2013-0431 — JRE

LOW

CVE-2013-0431 is a low-severity (CVSS 3.7) CWE-693 vulnerability in oracle jre. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-05-25) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, and OpenJDK 7, allows user-assisted remote attackers to bypass the Java…

Published

Jan 31, 2013

Updated

Oct 2, 2026

Affected

2 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-05-25 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-06-15.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2013-0431.

EPSS Exploitation Probability

via FIRST.org ↗

90.1%probability of exploitation in next 30 days

Very High Risk-0.09%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2013-0431 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, and OpenJDK 7, allows user-assisted remote attackers to bypass the Java security sandbox via unspecified vectors related to JMX, aka "Issue 52," a different vulnerability than CVE-2013-1490.

Affected Products

2 products · 12 configurations

Application

jreoracle

1 version

1.7.0

Application

openjdkoracle

1 version

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.

EDB-24539remotemultiple✓ Verified

Java Applet JMX - Remote Code Execution (Metasploit) (2)

by Metasploit · Feb 25, 2013

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every oracle jre deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2013-0431 yet — track the oracle jre advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
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. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 5	`java-1.7.0-openjdk-1:1.7.0.9-2.3.5.3.el5_9`	RHSA-2013:0247
Supplementary for Red Hat Enterprise Linux 5	`java-1.7.0-oracle-1:1.7.0.13-1jpp.1.el5_9`	RHSA-2013:0237
Supplementary for Red Hat Enterprise Linux 5	`java-1.7.0-ibm-1:1.7.0.4.0-1jpp.2.el5_9`	RHSA-2013:0626

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2013-0431 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works