A decade-old flaw in NGINX's HTTP/2 support, CVE-2026-123007, allows unauthenticated attackers to execute code on servers with HTTP/2 enabled. [1]
F5 announced on Wednesday patches for 22 total vulnerabilities, including five critical NGINX flaws named NGINX2Root. [2] F5 released patches for NGINX Open Source 1.30.7, 1.31.9 and NGINX Plus 37.0.8.1, 37.3.0.1. [3] The five NGINX2Root vulnerabilities have a CVSS severity score of 9.2 and allow unauthenticated remote code execution. [4]
Code executed through the flaw runs with the permissions of an NGINX worker process, and further privilege escalation may be required to gain root access. [5] The flaw, dubbed 'nginx2root,' has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. [6] Wiz stated that CVE-2026-123007 affects all NGINX versions released since 1.9.5 in 2015. [7]Una falla de 10 años en el soporte de HTTP/2 de NGINX, CVE-2026-123007, permite a atacantes no autenticados ejecutar código en servidores con HTTP/2 habilitado. [1]
F5 anunció el miércoles parches para un total de 22 vulnerabilidades, incluyendo cinco fallos críticos de NGINX denominados NGINX2Root. [2] F5 lanzó parches para NGINX Open Source 1.30.7, 1.31.9 y NGINX Plus 37.0.8.1, 37.3.0.1. [3] Las cinco vulnerabilidades NGINX2Root tienen una puntuación de gravedad CVSS de 9.2 y permiten la ejecución remota de código sin autenticación. [4]
El código ejecutado a través de la falla se ejecuta con los permisos de un proceso de trabajo de NGINX, y puede ser necesario un aumento de privilegios adicional para obtener acceso root. [5] La falla, bautizada como 'nginx2root', ha estado presente en el código de código abierto de NGINX desde la versión 1.9.5, lanzada el 22 de septiembre de 2015. [6] Wiz indicó que CVE-2026-123007 afecta a todas las versiones de NGINX lanzadas desde 1.9.5 en 2015. [7]
Proof7 sources · 2 publishers · signed
What this stands on
A decade-old flaw in NGINX's HTTP/2 support, CVE-2026-123007, allows unauthenticated attackers to execute code on servers with HTTP/2 enabled. · The Hacker News
F5 announced on Wednesday patches for 22 total vulnerabilities, including five critical NGINX flaws named NGINX2Root. · SecurityWeek
F5 released patches for NGINX Open Source 1.30.7, 1.31.9 and NGINX Plus 37.0.8.1, 37.3.0.1. · SecurityWeek
The five NGINX2Root vulnerabilities have a CVSS severity score of 9.2 and allow unauthenticated remote code execution. · SecurityWeek
Code executed through the flaw runs with the permissions of an NGINX worker process, and further privilege escalation may be required to gain root access. · The Hacker News
The flaw, dubbed 'nginx2root,' has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. · The Hacker News
Wiz stated that CVE-2026-123007 affects all NGINX versions released since 1.9.5 in 2015. · SecurityWeek
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · signed receipt ✓ · 7 sources · v 001The worldThe recordThe writingThe filing
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Thursday, November 19, 2026.
Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.