Skip to main content
Mallory
UnratedVulnerability

CVE-2026-114938: Java4Shell

Updated today
Trending this week#8of 427,955 vulnerabilities
Mention activity · 30 days102 mentions · peak 102 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-114938CWE-191

Java4Shell (CVE-2026-114938) is a reported memory-corruption vulnerability in OpenJDK's AVX-512-accelerated Base64 decoder. Preliminary technical accounts describe an integer underflow during final padding handling that causes a heap-based buffer overflow. A specially crafted 65-byte input reportedly produces a 62-byte overflow capable of corrupting adjacent Java objects. The reported affected range begins with OpenJDK 17.0.6 and includes subsequent Java 17 updates, but precise version and distribution applicability remain unconfirmed. Applications exposing the affected decoding path to unauthenticated input could potentially permit remote code execution. As of November 17, 2026, vendor confirmation of the CVE-specific technical details and affected range is unavailable.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could potentially execute attacker-controlled code with the privileges of the affected Java process, compromising application data and functionality. Heap corruption could also crash the JVM and disrupt services. Reliable code execution and exploitation in the wild have not been established.

Mitigation

If you can’t patch tonight, do this now.

Restrict unnecessary network exposure and access to services processing untrusted Base64 input. Potential temporary workarounds include disabling Base64 intrinsics with '-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics' or limiting AVX use with '-XX:UseAVX=2'. These measures are not confirmed workarounds and require vendor guidance and staging validation for applicability, effectiveness, and performance impact. Upstream rejection of malformed or oversized input may reduce exposure, but application-level validation must not be assumed to prevent vulnerable runtime processing.

Remediation

Patch, then assume compromise.

Install a runtime update explicitly confirmed by the relevant JDK vendor to address CVE-2026-114938. Update application-bundled runtimes and container base images, restart or redeploy affected services, and verify the builds used by running JVMs. No CVE-specific fixed build is confirmed; do not assume Oracle's November 2026 updates address this vulnerability without an explicit advisory mapping. Application dependency or logging configuration changes do not repair the reported runtime flaw.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
FAQ

Frequently asked questions

Is CVE-2026-114938 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-114938 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-114938?
As of Nov 17, 2026, Mallory has not confirmed a public exploit for CVE-2026-114938. 2 candidate exploit records are not yet analyzed.
Is there a patch for CVE-2026-114938?
Install a runtime update explicitly confirmed by the relevant JDK vendor to address CVE-2026-114938. Update application-bundled runtimes and container base images, restart or redeploy affected services, and verify the builds used by running JVMs.
Activity feed

Recent activity

102 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
sh3llc0d3 blogNews · Nov 17, 2026Java4Shell OpenJDK 17 CVE-2026-114938 | ShellcodeReported pre-authentication remote code execution vulnerability in OpenJDK 17.0.6 and subsequent 17.x builds using AVX-512 Base64 decoding intrinsics. An integer underflow causes a native heap buffer overflow. Exposure depends on services processing unauthenticated, untrusted Base64 input on AVX-512-enabled hosts. The content reports a preliminary CVSS v4.0 score of 9.2 and says verified patches are not yet available. Suggested temporary mitigations include staging-tested disabling of Base64 intrinsics and edge input validation. Exploit availability and actual exploitation are not established.Read more ↗rapid7 blogNews · Nov 17, 2026CVE-2026-114938: Reported Critical Pre-authentication Remote Code Execution in Java 17Reported critical memory corruption vulnerability affecting Java 17 and later that could permit unauthenticated remote code execution. The reported CVSSv4 score is 9.2, but the vulnerability details remain preliminary and await confirmation in Oracle or OpenJDK advisories.Read more ↗cyber security newsNews · Nov 17, 2026Critical Java 17 RCE Vulnerability Puts Servers at Risk as Oracle Releases 11 Security FixesAn unconfirmed, reportedly critical unauthenticated remote code execution vulnerability affecting OpenJDK 17.0.6 and later, with a reported CVSS 4.0 score of 9.2. Early reports suggest memory corruption, but the affected component and required configuration remain unknown. The CVE record is reserved, and Oracle has not linked its November Java fixes to this vulnerability. No fixed build, public proof of concept, or evidence of real-world exploitation has been published.Read more ↗cryptika blogNews · Nov 17, 2026Critical Java 17 RCE Vulnerability Puts Servers at Risk as Oracle Releases 11 Security Fixes | Cryptika CybersecurityReported critical unauthenticated remote code execution vulnerability affecting OpenJDK 17.0.6 and later, with a reported CVSS 4.0 score of 9.2. Early reports suggest memory corruption, but the CVE record remains reserved and the vulnerable component and exploitation prerequisites are unconfirmed. The article states that no fixed build, public proof of concept, or evidence of real-world exploitation has been published. Oracle has not linked its 11 Java SE fixes to this CVE.Read more ↗
+6 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity92Community discussion across Reddit, Mastodon, and other social sources.