CVE Intelligence
High

CVE-2018-2811 — Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Install). Supported...

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Install). Supported versions that are affected are Java SE: 8u162 and 10. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Java SE executes to compromise Java SE. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Note: Applies to installation process on client deployment of Java. CVSS 3.0 Base Score 7.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).

Published Apr 18, 2018 · Updated Oct 15, 2026 · Sources: 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.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.5% (30-day exploitation probability)+6
  • Technical severity (high)+6

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
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.49%
ahead of 41% of scored CVEs · Oct 15, 2026
Affects
Oracle
Java and 5 more
CVSS base
7.7
High · 2 source(s)

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
None
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.

  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

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 Java, Oracle Jdk, Oracle Jre…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Oracle Java version Java SE: 8u162version 10 Vulnerable CVE Program (cve.org) e CISA ADP
Oracle Jdk version 1.8.0-update162version 10 Vulnerable NIST National Vulnerability Database
Oracle Jre version 1.8.0-update162version 10 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server version 6.0version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Workstation version 6.0version 7.0 Vulnerable NIST National Vulnerability Database
Schneider Electric Struxureware Data Center Expert < 7.6.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

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

Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
7.7 CVSS 3.1 High 1.0 6.0 nvd@nist.gov via NIST National Vulnerability Database
7.7 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
3.7 CVSS 2.0 Low 1.9 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · oracle corporation/java
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Fix documented
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · oracle/jdk, oracle/jre, redhat/enterprise linux server, redhat/enterprise linux workstation, schneider-electric/struxure
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.7
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • 2018
  • CVE published
    Apr 18, 2018 · oracle

Source activity

Repeated readings are counted rather than listed.

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

References

10 on the record

Elsewhere on this site

Oracle
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-8045 XML External Entity (XXE) in Schneider Electric Struxureware Data Center Expert Jun 9, 2026
  • CVE-2026-34282 Uncontrolled Resource Consumption in Oracle Jre Apr 21, 2026
  • CVE-2026-34268 Exposure of Sensitive Information in Oracle Jre Apr 21, 2026
  • CVE-2026-22021 Uncontrolled Resource Consumption in Oracle Jre Apr 21, 2026
  • CVE-2026-22018 Allocation of Resources Without Limits or Throttling in Oracle Jre Apr 21, 2026
  • CVE-2026-22016 Exposure of Sensitive Information in Oracle Jre Apr 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 CWE classification.
  • 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-2018-2811 is "Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Install). Supported...", rated High. It affects Java (Oracle); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.7 describes technical severity. EPSS 0.49% 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.