How severe is CVE-2016-3427?

CVE-2016-3427 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-3427?

Affected package information for CVE-2016-3427 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2016-3427?

No fixed version has been published for CVE-2016-3427 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2016-3427 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2016-3427, including 1 in-the-wild exploitation 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-2016-3427?

CVE-2016-3427 has an EPSS (Exploit Prediction Scoring System) score of 93.3%, 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-2016-3427 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-3427 (Oracle Java SE and JRockit Unspecified Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-05-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-06-02. The required action was: Apply updates per vendor instructions. 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-2016-3427?

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

When was CVE-2016-3427 published, and has it been updated?

CVE-2016-3427 was published on April 21, 2016 and was last updated on April 16, 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·Added 2023-05-12 — agencies required to remediate by 2023-06-02

CVE-2016-3427

CRITICAL

Published

Apr 21, 2016

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

93.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java SE Embedded 8u77; and JRockit R28.3.9 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.

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.

Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java …

cisa.govCISAMay 2023

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-3427 in your stack?

O3 detects CVE-2016-3427 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works