# The 2Shell Vulnerabilities: React, PHP, Brotli, Java, NGINX, Ruby

React2Shell, PHP2Shell, HTTP2Shell, Java4Shell, NGINX2Shell, Ruby2Shell: what the 2Shell flaws have in common, which are exploited and what to do first.

Source: https://zyberum.com/insights/2shell-vulnerabilities-overview · Updated: 2026-11-19

Within twelve months, six flaws with a "2Shell" name were published, four of them within four weeks in autumn 2026. They are not related in code. What they share is the place: all of them sit in the platform under the application, in code that runs before the application sees the request and, in most setups, before anyone has logged in.

This page is the overview: what each one is, how urgent it is, and what the series means for operations. Each flaw has its own page with the mechanics, the detection and the actions.

## The six at a glance

| Name | CVE | Component | Published | Score | In the wild |
|---|---|---|---|---|---|
| [React2Shell](/insights/react2shell-cve-2025-55182) | CVE-2025-55182 | React Server Components, Next.js App Router | 3 Dec 2025 | CVSS 3.1: 10.0 | Yes, CISA KEV |
| [PHP2Shell](/insights/php2shell-cve-2026-109618) | CVE-2026-109618, CVE-2026-109619 | PHP engine, all web SAPIs | 21 Oct 2026 | CVSS 4.0: 9.2 | Yes, CISA KEV |
| [HTTP2Shell, Node2Shell, Brotli2Shell](/insights/brotli-http2shell-cve-2026-111497) | CVE-2026-111497 | Google Brotli decoder in Node.js, Python, .NET, Envoy and others | 22 Oct 2026 | CVSS 4.0: 9.2 | Listed in CISA KEV, attempts reported |
| [Java4Shell, Java2Shell](/insights/java4shell-cve-2026-114938) | CVE-2026-114938 | OpenJDK HotSpot, Base64 decoder on AVX-512 | 17 Nov 2026 | 9.2 (Calif), 8.1 (Oracle) | Not reported |
| [NGINX2Shell, NGINX2Root](/insights/nginx2shell-cve-2026-123007) | CVE-2026-123007, CVE-2026-123633 | nginx HTTP/2 | 18 Nov 2026 | CVSS 4.0: 9.2 (F5) | Not reported |
| Ruby2Shell | CVE-2026-132825 | Ruby string case conversion | 18 Nov 2026 | 7.4, maintainers: critical | Not reported |

Scores differ between scorers for almost every entry, mostly because of the attack complexity: several of these need an exploit that is tuned to the exact build. The table names who scored.

## What do they have in common?

They are reached before the application. A request passes the web server, may be decompressed, is parsed by the runtime and decoded by the framework. Only then does application code run and check who is asking. Every one of these flaws is in a step before that point.

Four more things repeat across the series:

- **Mostly memory safety.** Five of the six are memory corruption in C, C++ or assembly: use after free, out-of-bounds writes, an off-by-one. Only React2Shell is a logic flaw in JavaScript. Memory corruption is harder to exploit reliably, which is why some scores carry a high attack complexity, and why crashes are the first visible sign.
- **Bundled copies.** The Brotli decoder is compiled into Node.js. A JRE ships inside Keycloak, Jira and Jenkins. PHP sits in appliances. An operating system update does not reach these copies.
- **Restart discipline.** A patched package does nothing while the old process runs. PHP workers, JVMs and nginx master processes keep the old code until they are restarted, and container images until they are rebuilt.
- **Old code, new tools.** Several advisories credit AI-assisted research: the PHP advisories list OpenAI among the reporters, the Node.js advisory credits OpenAI's security tooling for the Brotli finding, and the Ruby advisory credits Ada Logics and Anthropic. Code that was considered settled is being read again, at scale.

## Ruby2Shell in brief

Ruby2Shell (CVE-2026-132825) is the weakest of the six and has no page of its own. Case conversion writes one byte past its buffer: in 14 legacy single-byte encodings the character "ß" becomes "SS", and the loop reserved room for one byte. The overflowing byte is always the letter S.

| | |
|---|---|
| Affected | Ruby up to 3.3.13, 3.4.0 to 3.4.12, 4.0.0 to 4.0.9; older lines get no fix |
| Fixed | 3.3.14, 3.4.13, 4.0.10 |
| Needs | Input in a legacy encoding such as ISO-8859-1 or Windows-1252 and a call to `upcase`, `swapcase`, `downcase(:fold)` or `casecmp?`. UTF-8, the Ruby default, is not affected |
| Reach | Rails and classic Sinatra apply `Rack::MethodOverride` before login, which upcases a form field |
| Assessment | The Ruby maintainers rate it critical and mention proof-of-concept code execution in some scenarios. OX Security calls reliable exploitation unlikely. No attacks reported |

Check `ruby -v` in the running process and the Ruby version of your images, including products that bundle Ruby, and update in your normal cycle.

## What to do first

Work by exposure and by what is exploited, not by the order of publication:

1. **React Server Components and Next.js** that are reachable from the internet: update, and treat systems that were unpatched in December 2025 as possibly compromised. [Details](/insights/react2shell-cve-2025-55182).
2. **Every PHP runtime**, mod_php and appliances first: update and restart all workers. [Details](/insights/php2shell-cve-2026-109618).
3. **Everything that decodes Brotli**: Node.js, Python services with the Brotli packages, .NET, Envoy and Istio. Rebuild images, because the decoder is bundled. [Details](/insights/brotli-http2shell-cve-2026-111497).
4. **Java 17 and later on x86-64**, identity providers and CI servers first: update every JDK including bundled ones, or set the interim flag. [Details](/insights/java4shell-cve-2026-114938).
5. **nginx with HTTP/2**: update and restart fully; a reload keeps the old binary. Check ingress controllers. [Details](/insights/nginx2shell-cve-2026-123007).
6. **Ruby**: update in the normal cycle.

## What the series means for operations

The individual fixes are routine. The lesson is in how long they took and why:

- **Know what runs.** The teams that were finished in a day could answer "where does PHP, Node.js, Java or nginx run, in which build" with a query. A software bill of materials per image and an inventory of appliances are the basis for everything else.
- **Patch the platform as fast as the application.** Base images, runtimes and web servers need the same pipeline as your own code: rebuild, test, roll out, restart, verify the running version.
- **Assume the first request succeeds.** Egress filtering, processes without privileges, read-only filesystems, no long-lived credentials within reach and isolated identity providers decide what a successful exploit is worth.
- **Watch for crashes.** For memory corruption, a series of crashed workers is the earliest signal. Treat it as a security event until explained.
- **Keep management interfaces off the internet.** A large share of the systems hit by PHP2Shell were administrative interfaces of appliances.

These are the same points a good [vulnerability management process](/insights/vulnerability-management-process) covers. A [penetration test](/web-application-pentest) checks whether they hold: we look at what an attacker reaches after the first step, because the next flaw of this kind will again be in a layer you did not write.

## FAQ

**What does "2Shell" mean?**

It is a naming habit, not a technical family. "X2Shell" stands for "from X to a shell": a flaw in X that can give an attacker command execution on the server. The pattern started with React2Shell in December 2025 and was reused for PHP, Brotli, nginx, Java and Ruby in autumn 2026. The names come from researchers and the press, the vendors mostly do not use them.

**Which of the 2Shell vulnerabilities are exploited in the wild?**

As of 19 November 2026: React2Shell and PHP2Shell are exploited and listed in the CISA KEV catalogue. The Brotli flaw is also listed in KEV; the public reports describe attempts. For Java4Shell, the nginx HTTP/2 issues and Ruby2Shell no attacks in the wild have been reported so far.

**Do I have to act if my own application code has no vulnerabilities?**

Yes. All of these flaws sit below the application: in the framework runtime, the language engine, a compression library, the JVM or the web server. They are reached before your code runs and mostly before authentication. A clean code review of the application says nothing about them.

**Where do I start?**

With the two that are exploited and reachable without conditions: Next.js and other React Server Components applications, and every PHP runtime including the ones inside appliances. Then Node.js, Python and proxies that decode Brotli, then Java on x86 servers with AVX-512, then nginx with HTTP/2, then Ruby.

## Sources

- [React: Critical Security Vulnerability in React Server Components](https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components)
- [PHP: release announcements 2026](https://www.php.net/archive/2026.php)
- [Node.js: October 2026 security releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases)
- [GitHub Advisory GHSA-9v8h-qqgm-4m35: out-of-bounds write in the Brotli decoder](https://github.com/advisories/GHSA-9v8h-qqgm-4m35)
- [Calif: Java4Shell write-up](https://calif.io/java4shell)
- [nginx security advisories](https://nginx.org/en/security_advisories.html)
- [Ruby: Multiple vulnerabilities in Regexp and String (18 Nov 2026)](https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/)
- [OX Security: Ruby2Shell, is it an actual risk?](https://www.ox.security/blog/ruby2shell-ruby-memory-corruption-flaws-expose-applications-to-remote-code-execution-but-is-it-an-actual-risk/)
- [CISA: Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)

## Related

- [React2Shell (CVE-2025-55182): How It Works, Detection, Fixes](https://zyberum.com/insights/react2shell-cve-2025-55182)
- [PHP2Shell (CVE-2026-109618/109619): Analysis, Detection, Fix](https://zyberum.com/insights/php2shell-cve-2026-109618)
- [HTTP2Shell (CVE-2026-111497): Brotli Decoder Flaw, Detection, Fix](https://zyberum.com/insights/brotli-http2shell-cve-2026-111497)
- [Java4Shell (CVE-2026-114938): JVM Base64 Flaw, Detection, Fix](https://zyberum.com/insights/java4shell-cve-2026-114938)
- [NGINX2Shell (CVE-2026-123007): nginx HTTP/2 Flaws, Detection, Fix](https://zyberum.com/insights/nginx2shell-cve-2026-123007)
- [Vulnerability Management: A Process That Works in Practice](https://zyberum.com/insights/vulnerability-management-process)
- [Your web app has a login. We check what is behind it.](https://zyberum.com/web-application-pentest)

---
Zyberum GmbH. Canonical page: https://zyberum.com/insights/2shell-vulnerabilities-overview
