← cd ../blog

The 2026 RCE field guide: 10 shell-access CVEs, triaged and ranked

Ten remote-code-execution flaws from 2026, ranked by what actually matters for defenders: exploitation status, authentication, and how much of your estate is exposed.

CVSS tells you how bad a bug could be. It doesn’t tell you what to patch first on a Monday morning. This guide ranks ten 2026 remote-code-execution flaws on three questions I actually triage by:

  1. Is it being exploited? A CISA KEV listing or a vendor confirmation beats any score.
  2. Does the attacker need credentials or a click? Pre-auth and zero-click go to the top.
  3. How much of a typical estate runs it? A bug in PHP or Node.js reaches more boxes than one in a niche appliance module.

Each entry links to a full write-up covering root cause, exposure checks, detection and remediation.

Scope and ethics. These are defensive summaries for prioritizing patching and hunting on systems you own or are authorized to assess. No exploit code here or in the linked posts.

Updated 20 Nov 2026: entries now link to the full write-ups published since this guide went up.

The ranking

# Vulnerability Score Pre-auth? Exploited? Fix
1 PHP2Shell, CVE-2026-109618 / 109619 9.2 (v4.0) Yes KEV PHP 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35
2 Node2Shell, CVE-2026-111497 9.2 (v4.0) Yes KEV Node 22.23.4 / 24.22.1 / 26.12.1; Brotli 1.2.1
3 F5 BIG-IP APM, CVE-2026-94127 9.8 Yes KEV F5 engineering hotfixes for 21.1 / 17.5 / 17.1
4 Citrix NetScaler, CVE-2026-88771 / 88772 9.5 (v4.0) Yes KEV 14.1-73.41 / 13.1-64.28 (also covers 88779)
5 Ivanti Connect Secure chain, CVE-2026-111357 / 118527 8.8 Yes, chained KEV 25.1.1.3 / 22.8R2.6
6 Apache Roller, CVE-2026-129448 9.8 Yes Yes (ASF) Roller 6.1.6
7 Plex2Shell, CVE-2026-96652 + 3 7.2 max per CVE Yes, chained KEV Plex Media Server 1.43.3.10861
8 Linux kernel TCP, CVE-2026-98432 9.8 Yes See post Distro kernel updates + reboot
9 Apache HTTP/2, CVE-2026-119618 9.8 Yes Not confirmed httpd 2.4.71
10 Java2Shell, CVE-2026-114938 8.1 (v3.1) Yes Not reported Nov 2026 JDK updates

Why this order

1–2: the runtime bugs. PHP2Shell and Node2Shell live in the language runtime, not an app or plugin. Every PHP site and every Node service that decodes Brotli inherits them, whatever framework sits on top. Both are on KEV, and PHP2Shell was seen in a honeypot four days before disclosure. If you only do two things this week, patch these two and restart the workers.

3–5: the edge appliances. F5 APM, NetScaler and Ivanti Connect Secure sit on the network edge by design, run as root, and are favorite initial-access targets for state-linked and ransomware crews. Each was exploited as a zero-day or within days. Patching isn’t enough: hunt for persistence first, because these appliances have a history of implants that survive upgrades. Ivanti’s own Integrity Checker missed the in-memory activity in this chain.

6–7: exploited, but narrower footprints. Apache Roller and Plex Media Server are less common in enterprise estates, but both were exploited. Plex is a reminder that “home” software ends up on corporate laptops and lab servers. No single Plex CVE scores above 7.2. Chained, they hand over the box, which is why per-CVE scores can mislead.

8–10: severe on paper, gated in practice. The kernel TCP bug and Apache HTTP/2 race are pre-auth 9.8s with huge potential reach, but reliable exploitation is hard, so they rank by exposure rather than evidence of attacks. Java2Shell needs an AVX-512 x86 CPU, a JIT-hot decoder and an application-specific chain to turn a 62-byte overwrite into a shell. Patch all three on your normal fast track. Don’t let them jump ahead of anything on KEV.

Also worth your attention

These didn’t make the top ten because they need credentials, a user action, or aren’t strictly remote code execution. Several are still on KEV and urgent:

A triage routine that works

# 1) Pull the current CISA KEV feed and list everything added in the last 30 days
curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json \
 | python3 -c 'import json,sys,datetime as d
c=(d.date.today()-d.timedelta(days=30)).isoformat()
for v in json.load(sys.stdin)["vulnerabilities"]:
  if v["dateAdded"]>=c: print(v["dateAdded"],v["cveID"],v["vendorProject"],v["product"])' | sort -r

# 2) Cross-check against what you actually run (examples)
php -v 2>/dev/null | head -1; node -v 2>/dev/null; java -version 2>&1 | head -1
httpd -v 2>/dev/null || apache2 -v 2>/dev/null; uname -r; ssh -V

Then for every match:

  1. Patch and restart. Runtimes, JVMs, PHP workers and kernels keep the old code in memory until restarted or rebooted.
  2. Hunt before declaring clean. For anything exploited pre-disclosure, look at process lineage from the vulnerable service, new admin accounts, web shells and outbound connections back to the date the vendor says exploitation began.
  3. Shrink exposure. Management interfaces, VPN admin portals and media servers shouldn’t face the internet.
  4. Verify from the outside. Re-scan after the change. A package on disk isn’t a patched process.

References

Verify every version against the vendor advisory before acting. Published 14 Nov 2026.