CVE-2026-47058 Deserialization in Oracle Java SE

High 7.4 Published Updated

Unauthenticated attackers can compromise Oracle Java SE via the Scripting component, leading to unauthorized data access and modification.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-47058?

CVE-2026-47058 is a high-severity unsafe deserialization vulnerability in Oracle Jdk, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Vulnerability in Oracle Java SE (component: Scripting). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf and 11.0.31. 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 creation, deletion or modification access to critical data or all Oracle Java SE accessible data as well as unauthorized access to critical data or complete access to all 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 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Weakness: CWE-502

Which versions are affected by CVE-2026-47058?

3 open source packages ship an affected version, including java, java-min and jre. It affects 2 products.

PackageAffectedFixed in
java BitnamiAll versions1.8.0, 8.0.501, 11.0.32
java-min BitnamiAll versions1.8.0, 8.0.501, 11.0.32
jre BitnamiAll versions1.8.0, 8.0.501, 11.0.32

Products include Oracle Jdk, Oracle Jre.

How do I fix CVE-2026-47058?

Upgrade java to a fixed version for your release line: 1.8.0, 8.0.501 or 11.0.32.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-47058 being exploited?

There is no known exploitation of CVE-2026-47058 in the wild and no public exploit code.

All Oracle Jdk vulnerabilities

Sources

Also known as BELL-CVE-2026-47058, BIT-java-2026-47058, BIT-java-min-2026-47058, BIT-jre-2026-47058, DEBIAN-CVE-2026-47058, GHSA-j75p-jh2f-6h9p and 8 more.

Is CVE-2026-47058 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free