· via dev.to (home feed)
Three pre-auth RCE disclosures hit OpenJDK, nginx and PHP; crawl data maps 58 million sites
A dev.to post pairs three pre-auth RCE disclosures in three days, an OpenJDK Base64 bug, five nginx flaws and a PHP security release, with crawl data from 58 million domains showing what the web actually runs.

Three disclosures in three days
A post on dev.to by the operator of a small web search engine documents an unusually dense run of security news: three pre-auth remote code execution vulnerabilities disclosed over three days in mid-November, affecting OpenJDK, nginx and PHP. What makes the post more useful than the disclosures alone is the evidence attached to it: statistics from the author's own crawl index of roughly 58 million domains, showing which server software those sites actually advertise.
The OpenJDK Base64 flaw
The first, nicknamed "Java4Shell," is CVE-2026-114938, a memory corruption bug in OpenJDK's Base64 decoder. According to the post, default configurations of Keycloak, Jira, Confluence, Jenkins and Artifactory are exposed to pre-auth remote code execution through it. Severity depends on who is scoring: the author reports Oracle rating it 8.1 while Calif rates it 9.2. Fixes shipped the same day, and no exploitation in the wild had been reported. The bug also does not appear in CISA's Known Exploited Vulnerabilities catalog as of the 2026.11.20 edition, which the post says contains 1,790 entries.
NGINX2Root
Disclosed November 18, "NGINX2Root" bundles five nginx flaws centred on unauthenticated remote code execution, with the two most severe rated 9.2. Fixes are available in nginx 1.30.7 and 1.31.9. As with the Java bug, the post reports no known exploitation, and none of the five CVEs appears in CISA's KEV catalog. The author is candid about open questions: the trigger conditions for the fifth CVE were unverified, and the network exposure of one internal nginx instance was still unknown at the time of writing.
The PHP security release
According to the post, November 19 brought PHP 8.6.0 alongside security releases for the older branches: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The headline fix is CVE-2026-115560, a session serializer RCE, accompanied by eleven further CVEs. Anyone on a supported branch has a direct upgrade path, and the 8.2 line, which many long-lived deployments still use, is covered by 8.2.36.
What the crawl data shows
The author's index covers about 58.2 million domains and 38.4 million pages, and its latest statistics generation on November 21 breaks down advertised server software: roughly 11.3 million domains behind Cloudflare, about 6.8 million running nginx, and 4.2 million on Apache. nginx is therefore the second most common server in the index, which is why a 9.2-rated unauthenticated RCE there has consequences measured in millions of sites, most of which the author expects will not be patched within the week.
The Java visibility gap
Java exposure is harder to quantify. The post explains that Java-based servers can be identified from Server headers, such as Jetty, Tomcat or Coyote, but Java versions almost never appear in those headers. The crawl can therefore show which sites run Java servers at all, not which ones are vulnerable. By contrast, the PHP version list the operator sells is built entirely from versions exposed in Server headers. The lesson cuts both ways: a version string in a Server header hands attackers reconnaissance for free, while sites that hide it force an attacker to guess.
A template for triage
The post also models a disciplined self-assessment. The author's serving path contains no Java, no nginx and no PHP, so the residual risks were evaluated case by case. A dormant OpenJDK install on a database machine was judged non-urgent because nothing executes it, and the machine's aging CPU lacks the AVX-512 VBMI instructions the buggy code path requires. An nginx 1.24.0 instance inside a container was ruled out because its configuration omits HTTP/2, QUIC, resolvers and mirrors. A PHP 8.2.35 internal dashboard, one patch release behind, was queued for an image rebuild, since the worst triggers do not apply but the core RCEs cannot be fully excluded from outside; the author notes that rebuild is being held for now.
Why it matters
The patching to-do list is concrete: upgrade nginx to 1.30.7 or 1.31.9, move PHP to the latest security release on your branch, and update or remove OpenJDK installations even where nothing appears to run them. The crawl data explains the urgency, because nginx trails only Cloudflare in the index and a pre-auth RCE there covers a fleet of millions. The broader hygiene point applies to anyone running a public site: inspect your own Server header. If it advertises a version, you have effectively published your attacker's shortlist yourself.
- #security
- #nginx
- #php
- #openjdk
- #web-servers