deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Attackers fire 150+ exploit attempts at newly patched Java flaw in one day

GreyNoise logged over 150 exploit-shaped requests in a single day against the newly patched Java flaw CVE-2026-114938. No intrusions are confirmed, but researchers expect reliable exploits within days.

Attackers fire 150+ exploit attempts at newly patched Java flaw in one day

Attackers have begun probing a serious Java vulnerability days after it was disclosed and patched, with security firm GreyNoise recording more than 150 exploit-shaped requests in a single day. No successful intrusion has been confirmed, but researchers expect reliable exploits to arrive within days.

The flaw, tracked as CVE-2026-114938 and nicknamed "Java4Shell", sits in the Java runtime itself rather than any single application. Security firm Calif disclosed it on 17 November 2026, and Oracle and the OpenJDK project shipped fixes the same day, according to SecurityWeek. CISA urged organizations to patch immediately and to check their inventories for Java, including copies bundled inside third-party applications. Calif described the bug as a memory flaw in how newer Java builds decode a common data format, and said that on some systems an attacker would not need a password.

Mass probing is already underway

According to SecurityWeek, GreyNoise had recorded more than 150 requests shaped like this attack, coming from five IP addresses, as of early 19 November. GreyNoise said it had seen no successful intrusions on its sensors. A separate firm, Previdian, reported nine exploitation attempts from six IP addresses on 18 and 19 November. That is an independent count that cannot be added to GreyNoise's figure, and Previdian could not confirm whether any target was compromised.

watchTowr told SecurityWeek that attackers are already scanning broadly across the internet and hitting its honeypots, including blind attempts with correctly shaped requests. Jake Knott, head of threat intelligence at watchTowr, described the activity as crude so far but said attackers are expected to refine more reliable, product-specific exploits over the coming days; SC Media published the same quotes on 18 November.

SecurityWeek also reported that Cloudflare's Cloudforce One team watched a scanner probe a target with a user agent that openly referenced the flaw, then return roughly 17 hours later carrying the exploit trigger while impersonating the Chrome browser.

No confirmed breaches yet

Despite the noise, the accurate description is attempted exploitation, not confirmed exploitation. Tenable's FAQ, updated on 18 November, says the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog, and a direct check of the catalog on 19 November found no entry for CVE-2026-114938. Cisco told SecurityWeek it has no knowledge of malicious use.

Weaponization nonetheless appears close. SecurityWeek and Tenable report that VulnCheck has a full exploit available to its customers. SC Media quotes Adrian Culley of SafeBreach saying unverified exploit code is appearing on GitHub, and Kevin Breen of Immersive has reportedly built a working exploit, though the reports do not say it has been publicly released.

Who is affected

The OpenJDK advisory marks newer builds of Java 17, 21, 25 and 27 as affected; standard Java 8 and 11 are not marked, and ARM-based systems are not affected. Because Java is often bundled inside other software, the practical risk for many organizations lies in self-hosted tools such as Jira, Confluence, Jenkins and Keycloak. SecurityWeek reports that Atlassian, the Jenkins project and the Keycloak team have begun issuing their own guidance, with Atlassian saying cloud customers need take no action while self-hosted and Data Center installations remain a separate question until patches arrive. Cisco has confirmed more than a dozen affected products with no fixes or workarounds yet, and Siemens says three of its Industrial Edge Management products are affected and recommends taking them offline while patches are prepared.

What to do now

The urgent step is the Java runtime itself. Anyone running self-hosted Java tools should confirm with their host, developer or agency that every instance is on a patched build from the November 2026 releases, and that the service was restarted, since the fix only takes effect after the Java process restarts. Where a patch cannot be applied immediately, official advisories describe a temporary Java startup setting that disables the affected fast path; a workaround is not a substitute for the patch. Researchers quoted by SC Media also advise keeping identity, build and collaboration consoles off the public internet, or behind a VPN, until they are patched.

Why it matters

The gap between disclosure and active probing has shrunk to about two days, and the sequence Cloudforce One observed, reconnaissance first and exploit delivery later, suggests attackers are working methodically. Java's presence inside countless third-party products makes this harder to inventory than a typical application bug, and vendors such as Cisco and Siemens still lack fixes. Nothing has been confirmed exploited yet, but the window before dependable, product-specific exploits appear is measured in days, which makes patching and restarting now far cheaper than responding to a breach later.

  • #java
  • #security
  • #vulnerability
  • #patching
  • #openjdk

Related posts