If your site or internal tools run on Java — including self-hosted software your agency or host may have installed for you — attackers have started probing a serious flaw in Java itself. The attempts are real. A successful break-in has not been confirmed.
On 19 November 2026, SecurityWeek reported that GreyNoise had recorded more than 150 requests shaped like this attack, coming from five IP addresses, as of early that day. GreyNoise said it had not seen any successful intrusions on its sensors. That 150-plus figure is GreyNoise's, as reported by SecurityWeek.
What happened
Security firm Calif disclosed the flaw, often called Java4Shell (CVE-2026-114938), on 17 November 2026. Oracle and the OpenJDK project released patches the same day. CISA urged organizations to patch immediately and to check inventories for Java, including copies bundled inside third-party applications. Calif described a memory bug in how newer Java builds decode a common data format, and said that on some systems an attacker would not need a password. This article does not include exploit steps.
What is new is the probing. Besides the GreyNoise count, SecurityWeek quoted watchTowr as saying attackers are already spraying the internet and hitting its honeypots, including blind attempts with correctly shaped requests. Jake Knott, head of threat intelligence at watchTowr, said the activity so far is not particularly functional, but that over the coming days attackers are expected to refine more reliable, product-specific exploits. SC Media published the same watchTowr quotes on 18 November 2026.
SecurityWeek also reported that Cloudflare's Cloudforce One team saw a scanner probe a target with a user agent that clearly referenced the flaw, then return roughly 17 hours later with the exploit trigger while impersonating the Chrome browser.
A separate firm, Previdian, told SecurityWeek its sensors logged nine exploitation attempts from six IP addresses on 18 and 19 November, and that this data cannot confirm whether any target was compromised. Those nine attempts are a separate sensor count. They should not be added to GreyNoise's 150-plus figure.
This is not a confirmed break-in
The accurate words are "attempts" and "probing," not "confirmed exploited." Tenable's FAQ, updated on 18 November 2026, says the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog. A direct check of that catalog on 19 November 2026 (catalog version 2026.11.18, released 18 November) also does not list CVE-2026-114938. GreyNoise and Previdian both say they have not confirmed a successful intrusion. Cisco told SecurityWeek it has no knowledge of malicious use.
SecurityWeek and Tenable report that VulnCheck has a full exploit available only to its customers. SC Media quotes Adrian Culley of SafeBreach as saying unverified exploit code is appearing on GitHub. Tenable and SecurityWeek also note that Kevin Breen of Immersive has reported building a working exploit; those reports do not say it has been released to the public. None of that is the same as a confirmed intrusion.
What this means if you run Java tools
For a typical small-business site, the practical question is whether any self-hosted Java-based tools are on a patched Java build. Examples of Java software businesses often run include Jira, Confluence, Jenkins and Keycloak. A confirmed break-in of those products has not been reported in the sources we reviewed. SecurityWeek does report that Atlassian, the Jenkins project and the Keycloak team have started issuing their own customer guidance. Atlassian, according to SecurityWeek, said cloud customers do not need to take action, while self-hosted and Data Center products are a separate question until patches are available.
SecurityWeek also reports that Cisco has confirmed more than a dozen of its products are affected, with no fixes and no workarounds yet, and that Siemens says three of its Industrial Edge Management products are affected and recommends taking those instances offline while it works on patches. Those vendor notes matter most if you run those products. For most site owners, the urgent step is still the Java runtime itself.
What to check today
1. Confirm the Java build is patched
Ask your host, developer or agency whether every self-hosted Java tool is running a patched Java build from the November 2026 releases. Then make sure the service was restarted, because a patch only takes effect after the Java process restarts. If you use a hosted version of a tool rather than a server you manage, ask the vendor or host whether their Java runtime is already patched.
2. If a patch cannot be applied today, use the vendor workaround
Official advisories describe a temporary Java startup setting that turns off the affected fast path until the patch can be installed. Ask your host or agency to apply the vendor's instructions and restart the service. A workaround is not a substitute for the patch.
3. Keep admin consoles off the open internet until they are patched
Researchers quoted by SC Media advise taking identity, build and collaboration consoles off the public internet, or putting them behind a VPN, until they are patched.
4. See what strangers can see
Patching one runtime does not tell you what else the site exposes from the internet. A free website security scanner can show what an outsider can see, without logging in. Our guide to how to tell if your website has been hacked covers practical signs to review if you are worried something already went wrong. You can also use the checklist in how to secure a WordPress website.
FAQ
Does this affect every website?
No. It depends on whether the site or its tools run an affected Java build, and on the kind of processor underneath. The OpenJDK advisory marks newer Java 17, 21, 25 and 27 builds for this flaw, and does not mark standard Java 8 or 11. ARM-based systems are not affected. If you are not sure what you run, ask your host or developer.
Has this been used in a successful attack?
No successful intrusion has been confirmed in the sources we reviewed. GreyNoise and Previdian both report attempts without a confirmed compromise, and the flaw is not on CISA's known-exploited list. That is not a reason to delay a patch. Experts quoted by SecurityWeek expect more reliable, product-specific exploits within days.
I only use a hosted tool. Do I need to do anything?
Ask the vendor or host whether their Java runtime is patched. According to SecurityWeek, Atlassian said its cloud customers do not need to take action. Self-hosted and Data Center installations are a different case: those need a patched Java build, or the vendor's temporary workaround, and a restart.


