Vulnary
← back to the feed
Critical· 9.8actively exploitedofficial fix available

CVE-2012-1723

A critical flaw in Oracle Java SE allows attackers to compromise the confidentiality, integrity, and availability of systems that run vulnerable Java versions. The vulnerability can be triggered remotely without any user interaction. Updating to a patched Java release removes the risk.

publishedJun 16, 2012
last modifiedAug 6, 2026
sourcesNVD · CISA-KEV
severity · cvss
9.8
critical · how bad it is
exploitation · epss
94%
100th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Oracle Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier.

02

Real-world impact

An attacker could read, modify, or delete data, disrupt services, or take full control of affected systems.

03

Why this severity

The CVSS score of 9.8 reflects that the flaw can be exploited over the network with no authentication, no user interaction, and it can fully compromise confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Update Oracle Java SE to the latest available version for your platform.
  2. 02Restart any Java applications or services to ensure the update takes effect.

CISA KEV required action

05

Timeline

  1. Jun 16, 2012 · Jun 16, 2012
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Mar 3, 2022 · Mar 3, 2022
    Confirmed exploited (CISA KEV)
    CISA added it to the Known Exploited Vulnerabilities catalog — attackers are using it in the wild.
  3. Mar 24, 2022 · Mar 24, 2022
    CISA remediation deadline
    Federal agencies are required to remediate by this date.
  4. Aug 4, 2026 · 2d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  5. Aug 6, 2026 · 4h ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →