CVE Intelligence
CISA KEV Low

CVE-2013-0431 — Oracle JRE Sandbox Bypass Vulnerability

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.

Published Jan 31, 2013 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: oracle

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • Public exploit/PoC (metasploit, exploitdb)+20
  • EPSS 90.2% (30-day exploitation probability)+15

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 25, 2022
EPSS FIRST
90.15%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Oracle
Jre and 1 more
CVSS base
3.7
Low · 4 source(s)
Prioritization reference: 5.3 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 15, 2022 — passed 1583 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Oracle Jre, Oracle Openjdk).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Oracle Jre version 1.7.0version 1.7.0-update1version 1.7.0-update10version 1.7.0-update11version 1.7.0-update2version 1.7.0-update3version 1.7.0-update4version 1.7.0-update5
and 3 more version 1.7.0-update6version 1.7.0-update7version 1.7.0-update9
Vulnerable NIST National Vulnerability Database
Oracle Openjdk version 7 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
3.7 CVSS 3.1 Low 2.2 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
3.7 CVSS 3.1 Low — — CISA-ADP via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
Sources disagree significantly and the divergence is under review. Every score is kept with its origin. For prioritization we use 5.3 (GitHub, Inc. via GitHub Security Advisories) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-693

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 25, 2022
Federal deadline
Jun 15, 2022
passed 1583 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 90.15%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before May 25, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · oracle/jre, oracle/openjdk
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 3.7
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    May 24, 2022 · CISA
  • 2013
  • CVE published
    Jan 31, 2013 · oracle

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

23 on the record

Elsewhere on this site

Oracle
every CVE for this vendor
2022-05
what else CISA listed that month
CWE-693
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-62574 Improper Access Control in Oracle Jre Jul 21, 2026
  • Medium CVE-2026-60526 Improper Input Validation in Oracle Jdk Jul 21, 2026
  • Low CVE-2026-60164 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
  • Low CVE-2026-60166 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
  • Medium CVE-2026-60147 Improper Access Control in Oracle Jre Jul 21, 2026
  • High CVE-2026-47063 Improper Access Control in Oracle Jre Jul 21, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2013-0431 is "Oracle JRE Sandbox Bypass Vulnerability", rated Low. It affects Jre (Oracle); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 3.7 describes technical severity. EPSS 90.15% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.