JreApplication · Oracle

CVE-2026-34282

HIGH · 7.5 CVSS v3.1 Published 2026-04-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Networking). Supported versions that are affected are Oracle Java SE: 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. 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.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Technical summary

dbcve analysis · high confidence

A vulnerability in the Networking component of Oracle Java SE and GraalVM allows unauthenticated remote attackers to cause a complete denial of service (DoS) via network access. Successful exploitation results in a hang or frequently repeatable crash of the affected Java environment.

MitigationApply the Oracle Critical Patch Update containing the fix for CVE-2026-34282, or upgrade to a patched version of Oracle Java SE (8u481+, 11.0.30+, 17.0.18+, 21.0.10+, 25.0.2+, or 26+) or GraalVM as specified in Oracle's security documentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JreApplication

Affected:= 1.8.0= 11.0.30= 17.0.18= 21.0.10= 25.0.2= 26

JdkApplication

Affected:= 1.8.0= 11.0.30= 17.0.18= 21.0.10= 25.0.2= 26

GraalvmApplication

Affected:= 21.3.17

Graalvm For JdkApplication

Affected:= 17.0.18= 21.0.10

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Java version

Run 'java -version' or 'java -fullversion' from the command line to obtain the exact version string

Affected if The reported version matches exactly 1.8.0, 11.0.30, 17.0.18, 21.0.10, 25.0.2, or 26 for Oracle JDK/JRE; 21.3.17 for Oracle GraalVM; or 17.0.18/21.0.10 for Oracle GraalVM for JDK
Verify Java process exposure to network

Review running Java processes and check if they bind to network ports (using 'netstat -anp' or 'ss -tlnp' on Linux, or 'netstat -an' on Windows)

Affected if Java processes are listening on network ports and accessible from untrusted network segments
Determine if untrusted code execution is possible

Check if Java Web Start (javaws) or browser applet plugins are enabled, or if the environment runs code from untrusted sources

Affected if Users can run Java Web Start applications or applets with untrusted code, or the system accepts untrusted Java code via APIs

Your environment is affected if you run an exact affected version listed above AND have Java processes exposed to network access or allow execution of untrusted Java Web Start/applet code.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the Oracle Critical Patch Update containing the fix for CVE-2026-34282, or upgrade to a patched version of Oracle Java SE (8u481+, 11.0.30+, 17.0.18+, 21.0.10+, 25.0.2+, or 26+) or GraalVM as specified in Oracle's security documentation.

Recommended fix High confidence

Oracle Java SE 8u511+, 11.0.25+, 17.0.12+, 21.0.6+, 25.0.4+ / Oracle GraalVM for JDK 17.0.19+, 21.0.11+ / Oracle GraalVM Enterprise Edition 21.3.18+

Identify the exact Java/JDK version currently installed (java -version)
For Oracle Java SE 8: Upgrade to JDK 8u511 or later
For Oracle Java SE 11: Upgrade to JDK 11.0.25 or later
For Oracle Java SE 17: Upgrade to JDK 17.0.12 or later
For Oracle Java SE 21: Upgrade to JDK 21.0.6 or later
For Oracle Java SE 25: Upgrade to JDK 25.0.4 or later
For Oracle GraalVM for JDK 17: Upgrade to version 17.0.19 or later
For Oracle GraalVM for JDK 21: Upgrade to version 21.0.11 or later

Caveat Minor. This is a security fix for a denial-of-service vulnerability; backward compatibility is expected. However, always test in a staging environment before production deployment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jre Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-34282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34282 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-34282?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Jre

Remediation

A high-priority fix

Fix this in Jre 18 hrs · Low

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-34282 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References