Overview
On November 17, 2026, Oracle released fixes for CVE-2026-114938 in its November Critical Security Patch Update. Researchers at Calif disclosed the flaw, nicknamed “Java4Shell,” as a memory-corruption vulnerability in OpenJDK’s Base64 decoder. Malformed Base64 input can enable remote code execution (RCE). Oracle scores CVE-2026-114938 8.1 on CVSS 3.1 with high attack complexity, while Calif rates it 9.2 under CVSS 4.0. Because the flaw is in OpenJDK code, it can also affect Java distributions from other vendors.
Salesforce is actively assessing its products, services, and infrastructure for potential impact. At this time, Salesforce has no evidence of exploitation affecting its systems or customer data. If we do, we will notify impacted customers.
Salesforce is following its vulnerability response processes and actively monitoring for malicious activity. At this time, we have no intelligence indicating threat actors are actively leveraging this vulnerability in the wild. However, customers should patch on an expedited schedule: the threat environment can change suddenly.
Guidance/Recommended Actions
- Update the Java runtime, not just the application. The flaw is in the Java standard library. Exposure depends on whether an application decodes attacker-controlled Base64 data. Remember to update Java runtimes bundled inside vendor products and container images.
- Check the hardware. Per Calif, the vulnerability is in machine-level code, making this hardware specific and dependents. Java uses the vulnerable code only on x86-64 processors that support AVX-512 VBMI. Red Hat lists Intel Ice Lake and newer, and AMD Zen 4 and newer specifically as potentially exploitable platforms. Red Hat also notes that ARM64 systems and older x86-64 CPUs are not potentially exploitable platforms. Calif notes in their advisory that on Linux, you can look for the avx512vbmi flag in the CPU flags using a script they provide.
- Prioritize internet-facing and authentication-handling systems. Calif says everyday functions such as authentication and file uploads can reach the vulnerable code.
- Restart after patching. Confirm that no running JVM is still on the old build.
- Check for signs of compromise. Patching will prevent future attempts to exploit the vulnerability, it will not remediate any post-attack actions that may have happened before patching. Check for signs of compromise and take action to remediate systems if they are found.
The Vulnerability
CVE-2026-114938: Out-of-bounds write in OpenJDK’s optimized Base64 decoder; potential unauthenticated remote code execution or memory disclosure.
The flaw sits in a performance shortcut Java uses to decode Base64 faster on certain Intel and AMD processors. A specially crafted Base64 string makes it write beyond the memory it set aside, which can corrupt other data the application holds.
Our analysis suggests that successful exploits and attacks will be developed on a per-application basis rather than universal targeting the vulnerability, narrowing the scope of potential attacks accordingly echoing the “careful exploitation” Calif’s advisory notes is required for this vulnerability.
This is because to achieve successful RCE, an exploit needs:
- A code path for the exploit code to reach Java’s decoder
- Objects in memory adjacent to the corrupted buffer that can be useful for the exploit code
- A means for the exploit code to observe or read the resulting memory state after an attempt to exploit the vulnerability
- An action within the application targeted by the exploit code that can be turned into execution
All of these conditions must be met for a successful exploit to be possible. Heap layout, allocation timing, and sometimes network timing differ by product and configuration all of which can be factors making a possible exploit more difficult, less likely and likely to be application specific.
Sources
- Oracle Critical Security Patch Update Advisory, November 2026
- OpenJDK Vulnerability Advisory, November 17, 2026
- Calif technical write-up
- Red Hat Security Bulletin RHSB-2026-018
- CVE-2026-114938 OpenJDK RCE (Java4Shell): Everything You Need to Know
Security resources
Curious about more ways to bolster the security of your Salesforce org? Check out our guide for additional guidance and resources


