The short version
- The family: Log4Shell, Spring4Shell and Text4Shell (2021–2022); React2Shell (December 2025); PHP2Shell and Node2Shell/HTTP2Shell (October 2026); Java2Shell/Java4Shell (reported November 2026).
- As of 17 November 2026 there is no CVE nicknamed Ruby2Shell, Go2Shell or Dotnet2Shell. The Ruby Brotli gem and .NET were affected by the Node2Shell bug, CVE-2026-111497.
- What they share: no login needed, in a component nearly every stack runs, weaponized within days, and once at least (PHP2Shell) exploited before the patch existed.
- What attackers do next is predictable: read environment variables and config files for credentials, then use them.
- The playbook: an inventory you can query, a patch path that's a pull request rather than a project, a honeytoken for the window, an undoable automatic response, and alerts kept as context.
1. Every *2Shell and *4Shell, in one table
| Name | CVE | Where the bug is | Disclosed | Status (17 Nov 2026) |
|---|---|---|---|---|
| Log4Shell | CVE-2021-44228 | Log4j 2 library: JNDI lookups in logged strings | Dec 2021 | Fixed; mass-exploited |
| Spring4Shell | CVE-2022-22965 | Spring Framework data binding on JDK 9+ | Mar 2022 | Fixed; exploited |
| Text4Shell | CVE-2022-42889 | Apache Commons Text string interpolation | Oct 2022 | Fixed; narrow real-world exposure |
| React2Shell | CVE-2025-55182 (CVE-2025-66478 rejected as a duplicate) | React Server Components; Next.js App Router | 3 Dec 2025 | Fixed; exploited within days; in KEV |
| PHP2Shell | CVE-2026-109618, CVE-2026-109619 | The PHP interpreter, every web SAPI | 20–22 Oct 2026 | Fixed 21 Oct; exploited before the fix; CVE-2026-109618 in KEV |
| Node2Shell / HTTP2Shell / Broccoli2Shell | CVE-2026-111497 | Google's Brotli decoder in Node.js, Bun, .NET, Envoy, Istio | 21–22 Oct 2026 | Fixed; exploitation reports disagree |
| Py2Shell / Python2Shell | CVE-2026-111497 | The same decoder in PyPI's Brotli and brotlicffi, used by requests, urllib3, httpx, aiohttp | 23 Oct 2026 | Fixed in Brotli 1.2.1, brotlicffi 1.2.1.0 |
| Java2Shell / Java4Shell | CVE-2026-114938 | Reported: OpenJDK 17.0.6+ (memory corruption) | 16–17 Nov 2026 | Reported, unconfirmed; no fix confirmed; no exploitation reported |
2. Names without a CVE (yet)
After Node2Shell, people online joked about the rest of the series: Ruby2Shell, Go2Shell, Dotnet2Shell, Rust2Shell. As of 17 November 2026, none of those is a real vulnerability name. If you got here searching for one, here's what's actually relevant:
- Ruby: the Ruby Brotli gem bundles the decoder affected by CVE-2026-111497 and has a fixed release. If your Ruby app decodes Brotli, update the gem. See Node2Shell.
- .NET: .NET 8, 9 and 10 were affected by the same bug where Brotli decompression is enabled, and fixed in 8.0.33, 9.0.22 and 10.0.14 on 25 October 2026. .NET Framework wasn't affected.
- Go: the standard library has no Brotli decoder. Third-party Go packages that wrap the Brotli C library were listed with fixed versions in the CVE-2026-111497 write-ups; check yours.
- Java: Java2Shell was a joke at the end of a conference talk on 14 November 2026 and a reported CVE three days later. Names can become real quickly; the playbook below doesn't depend on the name.
3. What they have in common
- No login needed. Each one is reachable by anyone who can send a request (or, for Py2Shell, anyone whose server you call).
- In a layer everybody runs. A framework default, the interpreter, the runtime, a compression library. Teams that never chose the vulnerable component still had it.
- Fast weaponization. React2Shell had a public exploit about a day after disclosure. PHP2Shell was attacked four days before the fix shipped, so no patch process, however fast, could have closed that window.
- Hidden copies. Next.js bundles its own React Server Components code; Node.js bundles Brotli; appliances bundle PHP and Java. "We upgraded the library" often isn't the same as "the running process is fixed".
- A predictable next step. After the shell, attackers read environment variables and config files for credentials, then use them. In our own React2Shell incident that's exactly what happened, and our alerts (CPU, egress, cost) were dismissed as a database migration.
4. A playbook for the next one
You can't know which runtime is next. You can make the next one boring. Five parts, roughly in the order they pay off:
- An inventory you can query. "Which internet-facing services run PHP 8.3 below .36?" should take minutes. That means knowing the image each running task uses, what each Dockerfile installs, and what each lockfile pins, linked to whether the workload faces the internet. Disclosure day is the wrong day to build that.
- A patch path that's a pull request, not a project. One pull request per repository with the version bumped, CI and the image build checked, and a rollback written down. A person merges. Critical, exploited, internet-facing findings shouldn't wait for someone to open a ticket.
- A tripwire for the window. There will be days between exploitation and the patch reaching production. A honeytoken, a decoy credential in each workload's environment that nothing legitimate uses, turns the attacker's predictable first move into an alert with almost no false positives, and tells you which workload it came from.
- One automatic, undoable response. Because a honeytoken trip is near-certain, it's safe to act on without a human: restart the container from its image, or deactivate the key. Both can be undone. That's the principle we call automate on certainty.
- Alerts as context, not triggers. Keep GuardDuty, Falco and your CPU and egress alerts. When a honeytoken trips, they explain what the attacker did. Automating on them directly means acting on symptoms that usually have innocent causes.
With that in place, our PHP2Shell incident was contained in under two minutes, ten months after React2Shell took four days.
5. Where Compass fits
Compass is our open-source (Apache 2.0) operations agent for AWS, and it implements four of the five parts:
- Inventory: its map records the images ECS task definitions run, Lambda runtimes and layers, what Dockerfiles install, and what manifests and lockfiles pin (Composer, npm, PyPI, Go, Cargo), with internet exposure from the network edges.
- Patch pull requests: the patch captain follows OSV, the CVE list, CISA KEV, EPSS and the Ubuntu, Debian, Alpine and Amazon Linux trackers every hour, matches every fifteen minutes, and opens the fix pull request without a click when a finding is exploited, likely to be, critical or internet-facing. It checks CI, the image build and an optional staging canary, and never merges. Today it covers PHP, Node and Python best; Java isn't on its default product list yet.
- Honeytokens: decoy AWS keys, database logins, S3 objects and SSH key pairs, planted as Terraform pull requests in your repository, each in one known place.
- Undoable response: on a trip, restart the ECS task or deactivate the key, gated by your policy, with a snapshot, verification, audit entry and rollback for each.
The fifth part, the alerts, you already have. Compass doesn't replace your WAF, GuardDuty or runtime monitoring, and doesn't stop the exploit request itself. More about Compass.
6. FAQ
What does "2Shell" mean in a vulnerability name?
It's shorthand for "from X to a shell": a bug that takes an attacker from sending a request to running commands on the server. The naming started with Log4Shell in 2021, then Spring4Shell and Text4Shell, and from React2Shell in December 2025 the "2Shell" form took over. It isn't an official classification; researchers and the press pick the nickname.
Is there a Ruby2Shell, Go2Shell or Dotnet2Shell vulnerability?
Not as of 17 November 2026: no CVE carries those nicknames. People joked about the series continuing after Node2Shell. However, the Ruby Brotli gem and .NET 8, 9 and 10 were affected by CVE-2026-111497, the bug called Node2Shell and HTTP2Shell, so if you run Ruby or .NET with Brotli decompression, check those fixes.
Are Node2Shell, HTTP2Shell, Python2Shell and Broccoli2Shell different bugs?
No. They're all CVE-2026-111497, an out-of-bounds write in Google's Brotli decoder, which Node.js, Python's Brotli packages, Bun, .NET, Envoy and Istio all ship. The name shifted as more runtimes were found to be affected.
Are Java2Shell and Java4Shell the same?
Yes, both names refer to CVE-2026-114938, a reported unauthenticated remote code execution in OpenJDK 17.0.6 and later. As of 17 November 2026 the details were not confirmed by Oracle or the OpenJDK project.
Which *2Shell vulnerabilities are in CISA's KEV catalogue?
React2Shell (CVE-2025-55182) and PHP2Shell's CVE-2026-109618 are in the Known Exploited Vulnerabilities catalogue. Reports disagree on whether CVE-2026-111497 (Node2Shell) was added. Java2Shell was not listed as of 17 November 2026. Check the catalogue directly, because it changes daily.
How do I prepare for the next *2Shell vulnerability?
Know what runs where, so you can answer "are we affected?" in minutes. Make patching a pull request per repository, not a project. Put a honeytoken (a decoy credential) in each workload's environment, because attackers read the environment first. Automate one undoable response on a honeytoken trip, such as restarting the container. And keep your alerts as context rather than triggers.
Written by Ilia Dubovskii, founder of Beamreach. CVEs, dates and statuses were checked against public advisories and security-vendor reporting on 17 November 2026. Java2Shell is still developing, and reports on Node2Shell's exploitation disagree; each page has the details and sources.
Related: React2Shell · PHP2Shell · Node2Shell · Py2Shell · Java2Shell · What to automate in incident response · One Fake Password Is Worth More Than 10,000 Alerts (talk)
Beamreach