Skip to content
-
Subscribe to our newsletter & never miss our best posts. Subscribe Now!
Today's News. Tomorrow's Perspective. Today's News. Tomorrow's Perspective.

Deliver fast, factual, and easy-to-understand news covering global events, technology, business, science, AI, health, entertainment, and lifestyle.

Today's News. Tomorrow's Perspective. Today's News. Tomorrow's Perspective.

Deliver fast, factual, and easy-to-understand news covering global events, technology, business, science, AI, health, entertainment, and lifestyle.

  • Home
  • Breaking News
  • Business
  • Sports
  • Health
  • Politics
  • Technology & AI
  • World
  • Home
  • Breaking News
  • Business
  • Sports
  • Health
  • Politics
  • Technology & AI
  • World
Close

Search

Subscribe
Critical Java4Shell flaw (CVE-2026-114938) allows RCE pre-authorization in Jira, Jenkins, Keycloak and more
Business

Critical Java4Shell flaw (CVE-2026-114938) allows RCE pre-authorization in Jira, Jenkins, Keycloak and more

jack colman
By jack colman
November 18, 2026 7 Min Read
Comments Off on Critical Java4Shell flaw (CVE-2026-114938) allows RCE pre-authorization in Jira, Jenkins, Keycloak and more
Critical Java4Shell flaw (CVE-2026-114938) allows RCE pre-authorization in Jira, Jenkins, Keycloak and more

A Java flaw called Java4Shell can allow accountless attackers to run their own code on Jira, Jenkins, Keycloak and three other widely used applications, says Calif, the security research firm that disclosed it this week.

The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on Intel and AMD x86-64 chips that support the AVX-512 VBMI functionality.

Tracked as CVE-2026-114938The patch was released today by Oracle and the OpenJDK project, whose open source code underpins many vendors’ Java releases. Amazon has patched its Corretto Java versions, but Red Hat is still preparing patches for its own.

The researchers are withholding their attack code for all six applications, and other labs have so far reproduced crashes and a memory leak but not code execution. Canada’s Cyber ​​Center said this week it was not aware of any attacks exploiting the flaw.

Servers often decode Base64-encoded data, such as HTTP Basic connection headers, SAML artifacts, and CSRF tokens, before checking whether a user is logged in. This is how an attacker without an account can exploit the flaw.

The flaw lies in a faster version of Java’s Base64 decoder that runs on chips with AVX-512 VBMI. Java goes there after compiling the decoder for speed, which it does for code that runs often.

A malformed string that ends with an extra = causes this decoder to write 62 or 63 bytes after its output has finished. Java rejects the string, but only after writing.

Bytes written after the end are fixed, so an attacker only controls where they land. For this reason, initial readings of the source code indicated a crash rather than a code execution, as The Hacker News noted in an earlier report yesterday.

The attacks worked without a connection with the default settings of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and with a connection on Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker, Calif said in its technical report. The researchers’ lists are incomplete and they rate the flaw at 9.2 out of 10 under CVSS 4.0.

They overflow fixed bytes by organizing server memory so that the overflow extends a neighboring array. They then use this array to write the bytes they want and a second array to read back memory, a step they call JavaBleed. From there, the researchers say, the attack reaches the parts of Java that execute code.

There is no single exploit that works everywhere. Each target requires its own memory configuration and timing, and some attacks are sensitive to network delays.

A proxy that expects full requests, as nginx does by default, blocks some but not all attacks. A failed attempt can crash Java and an attacker can often try again.

Security firm Upwind replicated the memory corruption on an AWS server with an Intel Ice Lake chip, where it corrupted the next object in memory and ultimately crashed Java, according to its lab’s results.

Blackpoint Cyber’s Adversary Pursuit Group crashed a Spring Boot test application by sending approximately 28,300 malformed login requests in about 20 seconds, without ever logging in.

The group also used the JavaBleed step in a local test to read a secret stored next to the overflow, which worked in all 30 runs. It did not replicate remote code execution, as its test results showed.

Oracle rates the flaw 8.1 out of 10 under CVSS 3.1, deeming it difficult to exploit but requiring no connection. The description in its CVE record states: “Successful attacks of this vulnerability may result in a takeover of Oracle Java SE. »

Red Hat also rates it as requiring no login, with a preliminary score of 9.8 out of 10. Amazon gives it an 8.8 out of 10 and describes the risk in its Amazon Linux entry as “a JVM crash for unauthenticated users or, in some application environments, code execution by an authenticated user with few privileges.”

The Canadian Cyber ​​Center also describes the flaw as remotely exploitable without authentication in its government alert.

The flaw was not listed in the KEV catalog of exploited vulnerabilities, maintained by the US Cybersecurity and Infrastructure Security Agency (CISA), when The Hacker News checked it today.

Who is exposed

The vulnerable code is found in Java 17.0.6 and later on the Java 17 line, as well as in Java 21, 25, and 27. Java 8 and standard Java 11 do not contain it, but Java SE 8 Performance Pack version 8u511b33-perf is affected. GraalVM for JDK 17.0.21.0.3, GraalVM for JDK 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3 are also affected.

It only works on x86-64 chips that support AVX-512 VBMI. These include Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids chips, as well as AMD Zen 4 or newer chips. ARM64 chips don’t run it.

Since the vulnerable code runs only on these chips, the same container image can run it on one server and not another. On Linux, this command indicates whether a server’s chip has the four features that the vulnerable code needs, and all four should appear in its output:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

The attacker also needs malformed Base64 to reach Java’s standard decoder, via paths such as the connection headers and tokens described previously.

Calif also says that a Java program that opens a TLS connection to a malicious server can be compromised, even if the program is not running any services of its own. The exploit came from another researcher, samczsun, and the researchers have not published how it reached the decoder.

Fixes and workarounds

The OpenJDK project’s vulnerability advisory lists the flaw as fixed in this week’s releases, and Oracle’s security advisory lists affected versions of its builds.

For Oracle Java, the fixed versions are the new .1 versions of the board, all released this week. The release notes for 17.0.21.1 say it includes the update’s security fixes, and the notes for 21.0.13.1, 25.0.5.1, and 27.0.1.1 say the same thing.

For Java 8 Performance Pack, the latest version is 8u513, available in Standard and Performance Pack versions. For GraalVM, the November security releases are GraalVM for JDK 17.0.21.1, GraalVM for JDK 21.0.13.1, and GraalVM Enterprise Edition 21.3.20.1.

Java versionAffected versionsCorrected version
OracleJava SE 1717.0.6 to 17.0.21.0.317.0.21.1
OracleJava SE 2121.0.13.0.3 and earlier21.0.13.1
OracleJava SE 2525.0.5.0.3 and earlier25.0.5.1
OracleJava SE 2727.0.1.0.3 and earlier27.0.1.1
Amazon Corretto 17, 21, 25 and 27Earlier versions, from 17.0.6 for Corretto 1717.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4
Azul Zulu 17, 21, 25 and 27Earlier versions, from 17.0.6 for Zulu 1717.70.201, 21.54.201, 25.38.201 and 27.30.201 (free versions)
Red Hat Enterprise Linux 8, 9 and 10 and Red Hat version of OpenJDK 17, 21 and 2517.0.6 and later, including 21 and 25None yet

The Corretto changelog for 17.0.21.1.2 lists the flaw as fixed, as do the changelogs for the newer versions 21, 25, and 27. Amazon Linux also marks its Corretto 17, 21, 25, and 27 packages as fixed.

Azul’s November update fixes the flaw in Zulu 17, 21, 25 and 27, according to its Zulu release notes.

Red Hat has not yet released patches for Red Hat Enterprise Linux 8, 9 and 10, nor for its OpenJDK versions 17, 21 and 25, according to its security bulletin. Containers based on its images must be rebuilt once the updated images are available.

SAP released SapMachine 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 this week, but their release pages don’t specify what they fix. Eclipse Temurin, Microsoft’s version of OpenJDK, and BellSoft Liberica did not list patched versions when The Hacker News checked today.

Products that bundle their own Java runtime environment require an update from the product manufacturer. After updating, restart Java services, then rebuild and redeploy the container images so that the running process uses the new version.

If you can’t update yet, start the JVM with one of these flags and remove it after the patched version is installed:

  • -XX:-UseBASE64Intrinsics only disables the faster Base64 code, which removes the vulnerable path and leaves other AVX-512 accelerations in place.
  • -XX:UseAVX=2 completely disables the AVX-512. Use it only on x86-64 servers, because Java on ARM64 does not recognize it and will not start.

In Upwind’s lab, both flags stopped overflow on every affected version tested. The company warns that another flag, -XX:DisableIntrinsic=_base64_decodeBlock, prevents Java from starting when used alone.

To spot attempts, he suggests checking the signs below, while cautioning that none of them proves compromise and their absence does not prove that a server is safe:

  • Base64 tokens of 32 characters or more ending in = and whose length is not a multiple of 4, especially in authorization headers
  • IllegalArgumentException error bursts from java.util.Base64$Decoder
  • Unexplained hs_err_pid crash logs or bursts of reboots

Malformed input that triggers the overflow was publicly released on September 9, in a proposed fix submitted to the OpenJDK code repository as a pull request. The proposal described an overflow in the same code of the AVX-512 Base64 decoder.

Its author closed it without merging it in early November, after an automated notification indicating that it had been inactive for more than eight weeks.

Gn bussni

Views: 3
jack colman
Author

jack colman

**Jack** is a staff journalist and digital content writer at **DailyVoxa**, specializing in breaking news, technology, artificial intelligence, business, and global affairs. He is passionate about transforming complex topics into clear, accurate, and engaging stories that help readers stay informed.With a strong focus on fact-based reporting and thorough research, Jack monitors developing events, analyzes reliable sources, and delivers timely news with clarity and context. His work emphasizes accuracy, transparency, and editorial integrity while avoiding sensationalism.At DailyVoxa, every article written by Jack follows the publication's Editorial Policy, Fact-Checking Policy, and Ethics Policy. He is committed to providing trustworthy journalism that empowers readers with reliable information and meaningful insights into the stories shaping the world.

Follow Me
Other Articles
CFP ranking overrated, underestimated: Alabama's influence defies logic, Indiana deserves better
Previous

CFP ranking overrated, underestimated: Alabama’s influence defies logic, Indiana deserves better

Why an SNL comedy skit about guarding went viral: NPR
Next

Why an SNL comedy skit about guarding went viral: NPR

Deliver fast, factual, and easy-to-understand news covering global events, technology, business, science, AI, health, entertainment, and lifestyle.
  • About Us
  • Accessibility Statement
  • Advertise With Us
  • AI Usage & Transparency Policy
  • Contact us
  • Cookie Policy
  • Corrections Policy
  • Meet Our Team
  • Privacy Policy
    • Disclaimer
    • DMCA & Copyright Policy
    • Editorial Policy
    • Ethics Policy
    • Fact-Checking Policy
  • Terms and Conditions
Copyright 2026 — Today's News. Tomorrow's Perspective.. All rights reserved.