Skip to main content

Oracle Java SE CVE-2026-83381

| EUVDEUVD-2026-106299 MEDIUM
Information Exposure (CWE-200)
2026-10-20 secalert_us@oracle.com GHSA-wh8h-835p-j93v
4.8
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed Java Security-component API
  2. Exploit
    Supply crafted untrusted input/data
  3. Execution
    Exploit flaw under high-complexity conditions
  4. Impact
    Gain partial read and unauthorized write to Java data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the target to expose the affected Oracle Java SE 'Security' component APIs to attacker-supplied data - typically an application or web service that passes untrusted input into those APIs - OR a deployment running sandboxed Java Web Start applications or Java applets that load and execute untrusted code and rely on the Java sandbox for isolation. The key LIMITING factor is the High attack complexity (AC:H): successful attacks depend on conditions the attacker cannot directly control, making exploitation unreliable. Server-side deployments that do not run untrusted code through these APIs are largely unaffected in practice, and modern environments have mostly retired the Java applet/Web Start client plugin, further shrinking the exposed surface. No authentication is required (PR:N) and no user interaction is needed (UI:N), but impact is confined to partial read and partial modify of a subset of Java-accessible data, with no availability impact.

Impact

This is a high-CVSS-does-not-apply case: the CVSS 3.1 base score is only 4.8 (MEDIUM), and the signals collectively point to low real-world urgency despite the ubiquity of Java. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N shows network reach and no authentication (PR:N), but attack complexity is High (AC:H), meaning exploitation depends on conditions outside the attacker's control, and impact is limited to partial confidentiality and integrity (C:L/I:L) with no availability impact (A:N). No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT on the CISA KEV list and no POC is referenced, so there is no public exploit identified at time of analysis. The only tag suggesting severity ('Authentication Bypass') is not corroborated by the Oracle description, which describes limited data read/modify access rather than a full auth bypass - treat that tag as unverified. Net assessment: a legitimate but low-priority patch-cycle item (part of the Oracle October 2026 CPU), not an emergency; the AC:H rating and absence of KEV/POC signals argue against widespread opportunistic exploitation.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends specially crafted input to an application that exposes the affected Oracle Java SE Security component APIs - for example via a web service that feeds data to those APIs - and under specific, hard-to-control conditions obtains partial read access and limited update/insert/delete access to Java-accessible data. Alternatively, a sandboxed Java Web Start application or applet loading untrusted code could exploit the flaw to partially bypass sandbox restrictions. No public exploit code is identified at time of analysis, and the High attack complexity makes reliable exploitation difficult.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Partial data disclosure and unauthorized modification in Oracle Java SE (8u503/8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1 and 27), plus Oracle GraalVM for JDK 17.0.20.1/21.0.12.1 and GraalVM Enterprise Edition 21.3.19.1.1, stem from a flaw in the 'Security' component that becomes reachable when an application or web service passes attacker-supplied data into those APIs, or when sandboxed Java Web Start/applet deployments execute untrusted code and rely on the Java sandbox for isolation. Network attackers need no credentials (PR:N) and no user interaction (UI:N), but High attack complexity (AC:H) means success depends on conditions the attacker cannot directly control, so exploitation is unreliable; impact is confined to partial read and partial modify of a subset of Java-accessible data with no availability effect (CVSS 3.1 base 4.8, MEDIUM). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.

RemediationAI

Apply the Oracle Critical Patch Update (October 2026) release for your JDK/JRE line - the advisory at https://www.oracle.com/security-alerts/cpuoct2026.html identifies the fixed update for Java SE 8, 11, 17, 21, 25 and 27, and GraalVM for JDK 17/21 plus GraalVM Enterprise Edition 21.3.x customers should take the corresponding CPU-aligned GraalVM release; exact patched build numbers should be confirmed from that advisory rather than assumed. Until the update is deployed, reduce reachability of the Security APIs: do not route untrusted input from web services, deserialization paths or templating engines into them, add input validation and, where object deserialization is involved, a JEP 290 serialization filter (jdk.serialFilter) - side effect is that overly strict filters break legitimate object graphs, so stage the filter before enforcing. Sandbox reliance on Java Web Start/applets is no longer a viable control (SecurityManager deprecated in JDK 17 via JEP 411 and permanently disabled in JDK 24 via JEP 486), so the durable mitigation for client-side deployments is removing applet/Web Start execution entirely rather than tuning the sandbox. Network-level restriction of untrusted clients to services that expose these APIs is a compensating control but costs functionality for legitimate external consumers. Patch available per vendor advisory.

Affected VersionsENISA

Oracle Java SE 8u503-perf
Oracle Java SE 17.0.20.1
Oracle Java SE 21.0.12.1
Oracle Java SE 27
Oracle Java SE 25.0.4.1
Oracle Java SE 8u503
Oracle Java SE 11.0.32.1

Affected Packages

euvd oracle_java_se no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected code sits in Oracle's 'Security' component of the JDK/JRE - the security-provider and sandbox-permission machinery historically used to enforce isolation for untrusted code (class loading, permission checks, cryptographic service providers). Oracle did not assign a CWE, so the root cause cannot be pinned to a specific weakness class from the data provided; the AC:H metric indicates the flaw requires a narrow window of conditions (specific API call sequences, configuration states, or timing/layout dependencies) that an attacker cannot directly engineer, which is why a network-reachable, unauthenticated, no-interaction vector still only yields partial confidentiality and integrity impact. The two realistic exposure paths are (1) server-side or middleware code that forwards untrusted input into the affected Security APIs, and (2) client-side sandboxed Java Web Start applications or applets running untrusted code and depending on the Java sandbox. That second path is largely historical: the applet/Web Start plugin has been retired and the SecurityManager was deprecated for removal (JEP 411, JDK 17) and permanently disabled (JEP 486, JDK 24), so the practical attack surface on current JDK 21/25/27 deployments is dominated by the first path. Aggregator tags include 'Authentication Bypass', but the assessed vector (PR:N, C:L/I:L/A:N) and the CVE description describe partial read/modify of a subset of Java-accessible data rather than a clean bypass of authentication, so that tag should not be read as a full login-bypass claim.

Know when Java gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 4.8 MEDIUM

Network-reachable APIs and no auth give AV:N/PR:N/UI:N; conditions outside attacker control force AC:H; impact is partial read and write only, so C:L/I:L/A:N, scope unchanged.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

Vulnerability in Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u503, 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1, 27; Oracle GraalVM for JDK: 17.0.20.1 and 21.0.12.1; Oracle GraalVM Enterprise Edition: 21.3.19.1.1. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE accessible data as well as unauthorized read access to a subset of Oracle Java SE accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 4.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Ubiquitous
Oracle Java SE/JDK runs across an enormous fraction of enterprise environments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Java

View all
CVE-2012-4681 CRITICAL POC
9.8 Aug 28

Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m

CVE-2015-7450 CRITICAL POC
9.8 Jan 02

Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti

CVE-2013-2465 CRITICAL POC
9.8 Jun 18

Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent

CVE-2011-3544 CRITICAL POC
9.8 Oct 19

Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug

CVE-2010-1871 HIGH POC
8.8 Aug 05

JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to

CVE-2012-1723 CRITICAL POC
9.8 Jun 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up

CVE-2013-0422 CRITICAL POC
9.8 Jan 10

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using

CVE-2012-0507 CRITICAL POC
9.8 Jun 07

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up

CVE-2015-4852 CRITICAL POC
9.8 Nov 18

The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers

CVE-2012-5076 CRITICAL POC
9.8 Oct 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow

CVE-2017-3066 CRITICAL POC
9.8 Apr 27

Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla

CVE-2012-0391 CRITICAL POC
9.8 Jan 08

The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy