nginx, Apache Roller, OpenJDK: Three Critical Flaws in 48 Hours
Same type of consequence — unauthenticated remote code execution — but three radically different exploitation statuses. We checked each case separately, and tested our own exposure rather than just discussing the theory.
November 19, 2026 · SunuCyberSecurity Team
critical flaws disclosed in 48h (Nov 17-19, 2026), three completely different ecosystems
CVSS v4.0 score for "nginx2root" — a bug hidden since 2015
CVSS v3.1 score Apache itself gives its Roller flaw, already under active exploitation
authentication required to exploit either nginx or Apache Roller
Sources: F5 (nginx's maintainer), ASF's oss-security mailing list, Datadog Security Labs — full detail at the end of this article
Between November 17 and 19, 2026, three critical flaws were disclosed in very different pieces of software: the world's most widely used web server (nginx), a lesser-known but very real Apache blogging platform (Roller), and the Java runtime itself (OpenJDK). All three share something that justifies attention: unauthenticated remote code execution. They differ sharply on everything else — practical severity, how confirmed each one is, and real exploitation status. Here's what we know, case by case, checked against primary sources rather than copied from a summary.
1. nginx "nginx2root" (CVE-2026-123007): a 2015 bug, found a decade later
nginx runs a sizeable share of the world's websites — as a front-end server or a reverse proxy, often without the teams operating it thinking about it day to day. The flaw, nicknamed "nginx2root," is a memory-corruption bug in HTTP/2 flow-control handling, present since version 1.9.5 (September 2015). It lets a remote client, with no authentication at all, execute code on any server where HTTP/2 is enabled.
Two nuances often lost in the headlines: exploitation also requires ASLR (a standard memory protection) to be disabled or bypassed, and the resulting code runs with the nginx worker process's own permissions — not directly as root. Taking full control of the machine needs a separate second step; one research team (Xint) demonstrated this by chaining the flaw to an unrelated Linux kernel bug (SCTP). So this is not "one click, the whole server" — it's a two-link chain.
CVSS score assigned by F5 (nginx's current maintainer): 9.2/10 on v4.0, 8.1/10 on v3.1. Affected versions: every Open Source release from 1.9.5 through 1.31.8, plus NGINX Plus 37.x and R34 through R36. Demonstrated by Wiz (bypassing ASLR), Xint, and analyzed by Rapid7. Proof-of-concept code exists on GitHub, but is explicitly scoped to a freshly started Docker container on the same machine — not a drop-in internet exploit; Rapid7's own version reportedly needs about 128 GB of HTTP/2 traffic and specific CPU features. No confirmed real-world exploitation as of writing, absent from CISA's KEV catalog. Fixed in 1.31.9 (mainline branch) and 1.30.7 (stable branch), plus NGINX Plus 37.3.0.1 and 37.0.8.1 — Ubuntu and Debian packages were still lagging at the time of writing. Mitigation until you can upgrade: disable HTTP/2 (the http2 off directive) and fully restart the service — a simple reload leaves old worker processes running.
2. Apache Roller (CVE-2026-129448): already exploited, and patched a second time
Apache Roller is an open-source blogging platform under the Apache project. The flaw sits in its XML-RPC endpoint, which deserializes vendor-extension data before even checking who's asking — letting an unauthenticated attacker reach code execution. CVSS score: 9.8/10 on v3.1 — not a third party's estimate, but the number Apache itself published on its own oss-security mailing list.
Notable detail: this is literally the same bug Apache already patched once in September 2026 under CVE-2026-82384 — but that first advisory only listed version 6.1.5 as affected. On November 17, Apache published a corrected advisory with a much wider range (4.0.0 through 6.1.4), under a new CVE number, and this time confirmed active exploitation. Apache has not shared technical details on how the attacks work or who is being targeted.
Fix: version 6.1.6 or later (6.1.7, released November 11 with 15 more CVE fixes, recommended). If you can't upgrade immediately: disable XML-RPC extensions (enabledForExtensions = false in WEB-INF/web.xml) or remove the /roller-services/xmlrpc servlet mapping, then restart.
3. OpenJDK "Java4Shell" (CVE-2026-114938): the least confirmed of the three
Reported by Calif, this flaw is described as an out-of-bounds write in OpenJDK, affecting Java 17.0.6 and later. One security vendor tracking it (Datadog) gives it a score of 9.2/10 on CVSS v4.0.
The same week, Oracle shipped its November quarterly Critical Patch Update, fixing 11 separate Java SE flaws — but its own release notes don't explicitly name CVE-2026-114938 among them. As of writing, we can't say with certainty whether Java4Shell is part of those 11 fixes, a distinct and still-unpatched issue, or something in between — sources themselves aren't aligned on this point. No public proof-of-concept, no confirmed real-world exploitation, absent from CISA's KEV catalog. Our recommendation: apply Oracle's November quarterly patch regardless (it fixes 11 real Java flaws either way) and watch for an explicit confirmation from Oracle or your OpenJDK distribution (Temurin, Corretto, Zulu).
What we know — and what we don't
Exploitation status differs sharply between the three. Apache Roller: active exploitation confirmed by the vendor itself. nginx: proof-of-concept code exists, but no confirmed real-world attack to date. Java4Shell: even the link to the same week's Oracle patch isn't firmly established. Treating all three as equivalent just because they share the word "critical" would be a prioritization mistake.
CVSS scores don't compare directly across the board. nginx and Java4Shell both show 9.2 on the CVSS v4.0 scale; Roller shows 9.8 on the older — but still widely used — v3.1 scale. The two scales don't read point-for-point; a 9.8 on v3.1 isn't automatically "worse" than a 9.2 on v4.0. Real exploitation status should drive prioritization, not the raw number.
A recurring pattern worth naming: AI-assisted discovery. The ASLR-bypass demonstration on nginx (Wiz) and the Java4Shell report (Calif) add to a pattern already covered on this blog with PHP2Shell in October (found by Wiz working with OpenAI): AI tooling is increasingly finding this class of bug before — sometimes well before — traditional manual audits. A trend worth watching, not a one-off.
Did we check our own exposure?
We don't run Apache Roller or any public-facing Java application anywhere in our own infrastructure — so those two don't apply to us directly, and we'd rather say so plainly than force a check that doesn't make sense.
nginx, on the other hand, is our reverse proxy on both of our production VPS. Checked directly rather than assumed: on sunutechnology.com and speedtest.sunutechnology.com, nginx 1.26.3 — a version technically inside the vulnerable range (1.9.5 to 1.31.8). But the real exploitation condition requires HTTP/2 to be negotiated: tested live from outside our network (openssl s_client -alpn h2) on both domains — neither one offers it. HTTP/2 isn't enabled on either real vhost. Same result on sunucybersecurity.com and this very blog (same host, same nginx version): no HTTP/2 negotiated at the origin.
On sunupulse.com, the external test does answer with HTTP/2 — but that's Cloudflare terminating the connection at its edge (confirmed by the Server: cloudflare header and the CF-RAY identifier), not our own origin nginx talking directly to the internet. Said plainly: an external test alone can't tell us anything about our own nginx's real HTTP/2 exposure in this specific case, since Cloudflare sits in front of it.
Honest conclusion: as of today, this flaw's specific exploitation vector doesn't apply to our infrastructure as currently configured. We're upgrading nginx to the fixed branch (1.31.9 / 1.30.7) on both VPS anyway — the same release fixes four other flaws that don't depend on HTTP/2. "Not exploitable today via this specific vector" isn't a reason to leave the update aside.
What to do now
Patch nginx even without HTTP/2 enabled
The same release fixes 4 other flaws (HTTP/3, DNS resolver, mail proxy) that don't depend on that same condition. "Not exploitable today via this specific vector" is not a reason to delay the update.
Check every vhost individually
Same lesson as PHP2Shell in October: the binary's version number doesn't tell the whole story. Test real ALPN negotiation (openssl s_client -alpn h2) on every exposed domain, not just the one you remember.
Upgrade Apache Roller to 6.1.7 without delay
If you run a Roller instance: Apache confirms active exploitation is underway. This isn't a theoretical bug.
Disable XML-RPC on Roller if you can't upgrade immediately
Set enabledForExtensions = false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart.
Apply Oracle's November Java patch
Even without explicit confirmation it covers Java4Shell, this patch fixes 11 real Java SE flaws — a reasonable move regardless of this specific uncertainty.
Don't prioritize by raw CVSS score alone
9.8 (Roller, v3.1 scale) isn't directly comparable to 9.2 (nginx and Java4Shell, v4.0 scale) — the two scales don't read point-for-point. Real exploitation status matters more than the number.
Sources and methodology
BastionZero, technical analysis of CVE-2026-123007 (affected versions, fixes, mitigation) · SSBCrack, independent cross-check (CVSS score, researchers involved) · oss-security mailing list, the Apache Software Foundation's own advisory for CVE-2026-129448 (CVSS score, active exploitation) · Security Affairs (relationship to CVE-2026-82384, 6.1.7 fix) · Corgea Research, technical analysis of the XML-RPC endpoint · Datadog Security Labs, CVE-2026-114938 (CVSS score, status still unconfirmed by Oracle) · The Hacker News. Our own infrastructure was checked live on November 19, 2026 (SSH access, real external ALPN tests on each domain). Data as of November 19, 2026 — the situation is evolving quickly on all three fronts, especially exploitation status; check the official advisories for the latest updates.
Related articles
Check your own exposure
A free scan, in a few minutes, no credit card required.
Free scanNewsletter
Get our next analyses
One email whenever we publish a new article. No spam, one-click unsubscribe.