Java4Shell (CVE-2026-114938): Frequently asked questions about OpenJDK remote code execution vulnerability
Java4Shell is a flaw in how Java decodes Base64 data. Calif, which found it, says it can let attackers run code on widely used Java applications without logging in. Oracle released fixed Java builds on November 17, and Calif is withholding its exploits for individual applications for now. Key takeaways CVE-2026-114938, dubbed Java4Shell, is an OpenJDK memory corruption vulnerability that Oracle scores 8.1 on CVSS 3.1, and Calif says its testing showed attackers could run code without logging in on applications such as Atlassian Jira and Jenkins. As of November 17, Tenable is not aware of any reports that attackers have exploited this flaw, though Calif has published a PoC that triggers the b
- Vendor
- Oracle
- Product
- Java SE / JDK
- CVSS v3.1
- 8.1
- EPSS
- 0.98 (p100)
- Exploitation
- public exploit code reported
- Exposure class
- Developer platform
Why it ranks 77 (Critical)
- Public exploit code reported
- CVSS v3.1 8.1 high
- EPSS 0.98 (high probability of exploitation)
- Product class: developer platform
- Widely deployed vendor product (Oracle)
- Covered by 15 independent sources
- Threat research
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- Tenable Research (tenable.com)
- CVE-2026-114938 on this site · NVD · CVE.org · Vulnpedia
- CVE-2013-0431 on this site · NVD · CVE.org · Vulnpedia
- CVE-2013-0422 on this site · NVD · CVE.org · Vulnpedia
- CVE-2013-2465 on this site · NVD · CVE.org · Vulnpedia
- CVE-2012-4681 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.