Subscribe
Cybersecurity

Java4Shell probing is confirmed in the wild, but no intrusion has been confirmed

Friday, November 20, 2026 · 5 min read

GreyNoise recorded 187 Java4Shell-shaped requests from five IP addresses as of early November 19, with zero confirmed intrusions on its sensors, while Cisco confirmed more than a dozen affected products; the verified fact is probing, not compromise.

Bearish$ORCL$CSCO

📊 Scorecard: our Bearish call on $ORCL is scored from $110.57, the last close before it ran. Its first result comes after the next close.

Java4Shell probing is confirmed in the wild, but no intrusion has been confirmed

The News

Probing for Java4Shell — the critical flaw in OpenJDK's Base64 decoder, disclosed and patched on November 17 — is now confirmed in the wild, but no successful intrusion has been confirmed. As of early November 19, the internet monitoring firm GreyNoise had recorded 187 Java4Shell-shaped requests from five IP addresses, with zero successful intrusions on its sensors.

Other monitors saw the same pattern. WatchTowr saw attackers spraying its global network of decoy systems with requests carrying 'java4shell-recon' user agents — the calling cards of scanning tools — alongside blind exploitation attempts. Previdian logged nine exploitation attempts from six IP addresses on November 18 and 19. And Cloudflare's Cloudforce One team saw scanners hiding their tools: one IP address probed with a Java4Shell user agent, then came back about 17 hours later with the exploit trigger disguised as an ordinary Chrome browser.

Vendors are rushing out impact lists. Cisco confirmed more than a dozen affected products, including Catalyst Center, Secure Network Analytics, Secure Workload, Smart Software Manager On-Prem, Splunk AppDynamics On-Premises Virtual Appliance and Intersight Virtual Appliance. Confluent, Tenable, Keycloak and Jenkins have published advisories and fixed builds. The flaw was still not on CISA's Known Exploited Vulnerabilities catalog as of November 19. This is new since our November 19 post, which covered the November 18 exploitation attempts — today's item is the November 19 probing counts and the vendor lists.

187 knocks on the door, zero break-ins — the probing is real, the compromise is not, and the gap between the two is the time defenders have left to patch.

Why It Matters

The distinction in this story is the whole story: probing is not compromise. Probing means attackers are knocking on doors to see which ones are unlocked — sending crafted requests and watching what comes back. A successful intrusion means they got in. GreyNoise's sensors recorded 187 knocks and zero break-ins, and no other monitor has reported a confirmed intrusion either. Some headlines have called this 'exploited in the wild', but the verified fact is probing, and the difference matters.

That said, probing at this speed is a warning, not a shrug. The flaw was disclosed and patched on November 17; within two days, scanners were already sweeping the internet for unpatched systems, and at least one was disguising itself as a normal browser to slip past defences. The history of flaws like this one is that probing comes first and real break-ins follow once attackers find the systems nobody patched.

The vendor lists show how wide the exposure is. Java runs inside an enormous range of products — network gear, analytics tools, identity software — so a flaw in a core Java component does not stay a Java problem for long. Cisco's list of more than a dozen affected products is only one vendor's; every company running Java-based software needs to check whether it is affected and apply the fix.

Analyst's Take

Our call is Bearish. Confirmed in-the-wild probing, 187 requests from five addresses within two days of disclosure, and a vendor list that keeps growing — including more than a dozen Cisco products — is a bad combination, even with zero confirmed intrusions so far. The window between disclosure and exploitation is now measured in days, and every unpatched system is a target that attackers have already found.

The hopeful note is that the patch exists and the flaw is not yet on CISA's exploited list, which means defenders who act now are still ahead of the attackers. The risk is the long tail: the companies that do not know they run affected Java, or that cannot patch quickly, will be the ones that show up in the next report. Watch for CISA adding the flaw to its catalog — that would mean a confirmed exploitation somewhere.

If you run Java-based software, the move is simple: check your vendor's advisory and patch. Oracle stewards OpenJDK and Cisco ships much of the affected gear, so both names are on this story for a reason. Reader poll: Have you patched for Java4Shell yet? Vote: Patched, Patching now, Not affected, Still checking.

Are you bullish or bearish on this story?

By The Numbers

187Java4Shell-shaped requests recorded by GreyNoise as of early Nov 19
5IP addresses the requests came from
0Confirmed intrusions on GreyNoise's sensors
12+Cisco products confirmed affected
9Exploitation attempts logged by Previdian from six IPs, Nov 18–19

FAQ

What is a CVE?

A CVE, or Common Vulnerabilities and Exposures number, is the standard ID for a publicly known security flaw. Java4Shell is CVE-2026-114938 — a flaw in OpenJDK's Base64 decoder, a piece of code that translates data between formats.

What is probing?

Probing is when attackers send test requests to systems across the internet to find ones that are vulnerable, without necessarily breaking in. It is the reconnaissance step — knocking on doors to see which are unlocked — and it usually comes before real attacks.

What is a honeypot?

A honeypot is a decoy system set up to look like a real target so researchers can watch attackers try to break in safely. WatchTowr's global honeypot network recorded Java4Shell scanning, which is how researchers know probing is happening.

What is CISA's KEV catalog?

The KEV, or Known Exploited Vulnerabilities, catalog is a list kept by the US Cybersecurity and Infrastructure Security Agency of flaws confirmed to be exploited in real attacks. Java4Shell was not on it as of November 19 — another sign that confirmed exploitation has not yet been established.

👁

Source: SecurityWeek

Get the daily briefing. AI news with a markets lens — tickers, bullish/bearish reads, zero hype. Subscribe free on Substack

More on $ORCL

All $ORCL coverage →

More from AI Agent Update