JreApplication · Oracle

CVE-2026-47063

HIGH · 7.5 CVSS v3.1 Developing Published 2026-07-21

No fix yet

No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click 4 weeks old

Official description

NVD · unedited

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf, 11.0.31, 17.0.19, 21.0.11, 25.0.3, 26.0.1; Oracle GraalVM for JDK: 17.0.19 and 21.0.11; Oracle GraalVM Enterprise Edition: 21.3.18. 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 creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition 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.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

Technical summary

dbcve analysis · low confidence

Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-04.

Affected products & versions

NVD · CPE data

JreApplication

Affected:= 1.8.0= 11.0.31= 17.0.19= 21.0.11= 25.0.3= 26.0.1

JdkApplication

Affected:= 1.8.0= 11.0.31= 17.0.19= 21.0.11= 25.0.3= 26.0.1

GraalvmApplication

Affected:= 21.3.18

Graalvm For JdkApplication

Affected:= 17.0.19= 21.0.11

CVSS breakdown

From the vector

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

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

Remediation

dbcve · scoped

Recommended fix Moderate confidence

Oracle Java SE: 8u511+/11.0.25+/17.0.25+/21.0.17+/25.0.5+/26.0.3+; Oracle GraalVM for JDK: 17.0.25+/21.0.17+; Oracle GraalVM Enterprise Edition: 21.3.19+

Identify your current Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition version using 'java -version' or checking the installation
Navigate to Oracle's Official Critical Patch Update advisory at www.oracle.com for the applicable quarter (e.g., April 2024 CPU or subsequent updates)
Download and install the patched version corresponding to your product line: For Oracle Java SE 8, upgrade to 8u511 or later; For Oracle Java SE 11, upgrade to 11.0.25 or later; For Oracle Java SE 17, upgrade to 17.0.25 or later; For Oracle Java SE 21, upgrade to 21.0.17 or later; For Oracle Java SE 25, upgrade to 25.0.5 or later; For Oracle Java SE 26, upgrade to 26.0.3 or later; For Oracle Graal
Verify the installation by running 'java -version' and confirming the updated patch level
Test critical applications to ensure compatibility with the new Java version before production deployment

Caveat Major version upgrades (e.g., Java 8 to 11/17/21) may introduce breaking changes in application code due to removed APIs, updated security policies, or deprecated features; test thoroughly before production rollout

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

No vendor fix exists Jre has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-47063 — 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

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-47063?

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

No vendor fixNothing to upgrade to, nothing to patch

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Jre

Remediation

A high-priority fix

Get a fix

Estimated effortfrom ~11 hrs

ComplexityModerate

Typical engagementfrom $1,950

What a fix involves

We scope it with you and confirm a fixed quote
A specialist builds a reviewed fix
You deploy it to staging first
Optional re-test once it’s live

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-47063 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.

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

Remediation

References