Cloudanix VulnDB

CVE-2026-91332

Medium · 5.3

CVSS

5.3

EPSS

0.3%

Published

Oct 20, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A problem in Java lets someone on the network change certain data inside applications without needing any login or special access.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Data Tampering
Component
Library
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Medium

What it actually does

Improper input validation in the Networking component permits unauthenticated remote attackers to supply crafted data via multiple protocols or APIs, resulting in unauthorized modification (insert/update/delete) of accessible application data without affecting confidentiality or availability.

Why it matters to the business

Attackers can silently alter data processed by Java applications or sandboxed applets, potentially leading to corrupted records, tampered transactions, or manipulated outputs in client-side or server-side deployments; low exploitation likelihood and four days since disclosure keep immediate operational risk modest.

How an attack unfolds

An attacker sends specially crafted network requests or supplies malicious data through exposed Java APIs (such as those used by web services) that reach the vulnerable Networking component; because input validation fails, the malformed data is accepted and causes unauthorized changes to in-scope data structures before any further processing occurs.

How to fix it

Apply the latest Oracle Critical Patch Update that addresses this issue for each affected Java SE and GraalVM version; disable or restrict network-accessible APIs where possible until patches are deployed; monitor Oracle release notes for exact per-version fixes as they become available.

How to confirm the fix worked

After patching, confirm the updated Java version string no longer matches the listed vulnerable releases and test that previously successful malformed inputs are now rejected; re-run application-specific API tests to verify integrity controls function as expected.

Typical attack path

  1. Identify a reachable Java SE or GraalVM instance exposing Networking APIs or handling untrusted input.
  2. Craft and transmit network payloads or API calls containing invalid or maliciously formed data.
  3. Trigger the improper validation path to achieve unauthorized data modification.
  4. Observe or leverage the resulting data changes for further impact.

How to detect it

Search application and network logs for repeated malformed requests to Java Networking APIs or unusual data modification patterns originating from untrusted sources; correlate with sandboxed applet or Web Start execution events if untrusted code is loaded.

What your security team should do

  • Prioritize patching Oracle Java SE and GraalVM deployments within standard change windows given the low EPSS and absence from KEV.
  • Review and restrict exposure of Networking APIs or sandboxed Java code that accepts external input.
  • Update vulnerability scanning policies to flag the affected versions until remediation is complete.

The record

Vulnerability in Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 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. Easily exploitable 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. 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 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities