Hackers Exploiting Java4Shell RCE Flaw Using ARTEX Disguise Themselves as Chrome

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Cloudflare’s Cloudforce One reported a Java4Shell exploit attempt that looked like ordinary Google Chrome traffic in web logs. The team said a source IP first scanned a target using a User-Agent header that gave away the scanning tool. About 17 hours later, the same address sent an exploit attempt to the same target, this time claiming to be Chrome.

In a separate November 18 update, Cloudforce One said it had seen traffic linked to both ARTEX and Java4Shell from a single IP address for the first time.

The two updates do not establish that ARTEX sent the Chrome-disguised request or that either attempt led to a breach. The disguise was in the HTTP User-Agent header, which identifies the client making a web request, not in Chrome itself.

Java4Shell Puts Java Servers at Risk

Java4Shell, tracked as CVE-2026-114938, affects the Base64 decoder in OpenJDK’s HotSpot runtime. Base64 is a common way to represent binary data as text. On affected systems, the decoder can write outside its assigned memory when it processes invalid input. The flaw can crash a Java service, expose data held in memory, or allow remote code execution (RCE), meaning an attacker can run code on the target.

As Cyber Security News reported in its Java4Shell coverage, the flaw is in the Java runtime itself, not a library such as Log4j. It requires an unpatched Java build, an x86-64 processor with AVX-512 VBMI support, and an application that passes attacker-controlled data to the affected decoder. ARM64 systems do not use that vulnerable code path.

Calif’s research demonstrated code execution without a login in default test setups of Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory, and PingFederate. Those tests show what is possible under the right conditions. They do not show that the target in Cloudforce One’s report was running any of those products or that the request succeeded.

The FBI’s November 13 advisory describes ARTEX as an AI-driven security testing framework that attackers have used to speed up intrusions. It cites separate campaigns involving South Korean financial institutions and ConnectWise Cloud Backup customers. Cyber Security News has also covered ARTEX consoles exposed to the internet. Neither report ties those earlier findings to the Java4Shell request that posed as Chrome.

Oracle and OpenJDK released fixes on November 17. Fixed OpenJDK builds include 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1. Administrators should check their Java vendor’s advisory and prioritize internet-facing services. After restarting a service, verify the Java version it actually loads, not just the version returned by the host’s default Java command.

For incident review, compare web and application logs for repeat requests to the same service, then check host logs for unexpected Java crashes or unusual activity.

A Chrome label is not proof that a real browser sent the request, and a shared IP is not proof of a common operator. The FBI advises checking IP indicators against current network activity before using them to block traffic.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

The post Hackers Exploiting Java4Shell RCE Flaw Using ARTEX Disguise Themselves as Chrome appeared first on Cyber Security News.