NGINX2Root: nginx HTTP/2 Flaw CVE-2026-123007 (CVSS 9.2) Allows Unauthenticated RCE in Every Release Since 2015, Public PoC Out and a Kernel Chain to Root — Update to 1.30.7 or 1.31.9

Cyber · 2026-11-19 · By H.A

NGINX2Root: nginx HTTP/2 Flaw CVE-2026-123007 (CVSS 9.2) Allows Unauthenticated RCE in Every Release Since 2015, Public PoC Out and a Kernel Chain to Root — Update to 1.30.7 or 1.31.9

F5 fixed ten nginx flaws on 18 November, including five rated CVSS 9.2 and an HTTP/2 flow-control bug (CVE-2026-123007) that researchers exploited in default setups with ASLR bypassed, and chained with an unpatched Linux SCTP kernel bug to get root.

What Happened

On 18 November 2026, F5 shipped nginx 1.30.7 (stable) and 1.31.9 (mainline). The two releases fix ten vulnerabilities in the open-source web server. Five of them are rated 9.2 under CVSS 4.0 and can lead to remote code execution. The most serious one, CVE-2026-123007, is a memory corruption bug in HTTP/2 flow control. It sits in code that every official release since nginx 1.9.5 (2015) contains, and the researchers say it can be reached in a default HTTP/2 setup with nothing behind nginx but static files.

One of the research teams calls the set "NGINX2Root". At least five groups reported the bugs on their own: an AI security company, a cloud security vendor and three other research teams. The AI company says its automated platform found four of its five reported flaws with no human guidance. It also says it chained the HTTP/2 bug with an unpatched Linux kernel flaw to get root on the host, even from inside a Docker container.

No attacks in the wild had been reported at the time of writing. However, one of the research teams released a proof-of-concept exploit for CVE-2026-123007 on disclosure day. Nginx runs roughly three in ten websites whose server software can be identified, and it is everywhere as a reverse proxy, load balancer and Kubernetes ingress. That makes this the patch to do first this week.

The Two HTTP/2 Bugs

Both HTTP/2 flaws need HTTP/2 to be turned on, and most public nginx servers serving TLS turn it on.

The public proof of concept for CVE-2026-123007 is heavy. According to the researchers, it needs about 128 GB of HTTP/2 traffic over a single connection, and its authors noted that other exploitation methods "may be viable, but none are currently known". That much traffic is a real obstacle, but it is not a defence. A long-lived HTTP/2 connection moving huge amounts of data is exactly the signal defenders should look for.

The Other Critical Flaws

The same releases fix three more bugs rated 9.2 that depend on configuration:

Lower-rated fixes include an infinite loop when reading a request body over TLS 1.3 (CVE-2026-118899, a denial of service), a NULL pointer crash with PROXY protocol v2 (CVE-2026-120993, only in 1.31.4–1.31.8), a buffer overflow when alias is combined with try_files (CVE-2026-125283), an SNI bypass in stream client-certificate checks (CVE-2026-120967) and weak validation in the stream ssl_preread module (CVE-2026-123640).

The Root Escalation

On its own, code execution through CVE-2026-123007 runs with the rights of an nginx worker process, which are normally limited. The AI research company says it chained this with a bug in the Linux kernel's SCTP (Stream Control Transmission Protocol) code that dates back to Linux 4.15 (2018). In its tests, a compromised worker reliably became root on the host, including from inside a container. The kernel bug has no CVE and no patch yet, and the company is holding back details until a fix exists.

Most web servers never use SCTP. Blocking the module from loading takes the escalation path away until a kernel fix arrives. Note that this does not unload a module that is already loaded, and it does not help if SCTP is built into the kernel.

Who Is Affected

What To Do Now

Defensive commands to check versions and apply the stopgaps:

# Show the installed version and whether HTTP/2 is enabled
nginx -v
nginx -T 2>/dev/null | grep -nE 'http2|listen .*ssl'

# Temporary: in each affected server block set
#   http2 off;
# then test and reload
nginx -t && systemctl reload nginx

# Block SCTP from loading (does not unload a module already loaded)
echo "install sctp /bin/false" | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep -i sctp

Why It Matters

This is one of the biggest web-server patch events in years. One bug, ten years old, sits in the default HTTP/2 path of software that serves a large share of the internet. It also shows a pattern we have reported on several times this month: several teams, some of them using AI systems, found the same flaws within weeks of each other. Once researchers and AI tools can find bugs this fast, attackers will be able to as well. With a public proof of concept already out, the safest course is to treat the time to patch as hours, not weeks.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.