[{"data":1,"prerenderedAt":241},["ShallowReactive",2],{"seo-verification":3,"blog-nginx2root-cve-2026-123007-update-nginx-http2-ma-en":6,"promo-bar-likely":240},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-nginx2root-cve-2026-123007-update-nginx-http2-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":28,"featuredImage":30,"bgImage":31,"posterImage":32,"relatedSolution":30,"intro":33,"keyPoints":34,"sections":35,"ctaTitle":183,"ctaBody":184,"ctaButton":185,"ctaUrl":186,"relatedPosts":187},588,"nginx2root-cve-2026-123007-update-nginx-http2",{"fr":12,"en":10,"ar":13,"es":14},"nginx2root-cve-2026-123007-http2-mettre-a-jour-nginx","nginx2root-cve-2026-123007-تحديث-nginx-http2","nginx2root-cve-2026-123007-actualizar-nginx-http2","nginx2root CVE-2026-123007: update nginx for HTTP\u002F2","nginx2root (CVE-2026-123007) affects nginx with HTTP\u002F2 enabled. Fixed versions by distribution, exposure commands, restart, Docker and a workaround.",11,0,false,"2026-11-20T00:00:00+00:00","2026-11-21T14:39:55+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},8,"Security & Monitoring","securite-monitoring","bg-rose-500\u002F10 text-rose-400","security",[29],{"id":23,"name":24,"slug":25,"color":26,"icon":27},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fnginx2root-cve-2026-123007-http2-mettre-a-jour-nginx-poster.svg","On November 18, 2026, nginx released the security versions 1.30.7 (stable) and 1.31.9 (mainline). They fix several flaws, including CVE-2026-123007, a memory corruption in HTTP\u002F2 flow control nicknamed \"nginx2root\". On a fleet of client servers, the question comes down to three points: is HTTP\u002F2 enabled, which version is really running in memory, and is the fix loaded? This guide gives you the commands to answer in under an hour, then to fix and check each server.",[],[36,40,72,75,97,100,140,143,164,167,171,174,177,180],{"type":37,"title":38,"body":39},"h2","What was released on November 18, 2026, and why it is serious","The disclosure was coordinated: on November 18, 2026, nginx.org released version 1.30.7 on the stable branch and 1.31.9 on the mainline. The 1.30.7 change log lists, along with the HTTP\u002F2 flaws, a defect involving `try_files` and `alias` (CVE-2026-125283) and several other fixes.\n\nOn severity, two sources complement each other and should be quoted as they stand. The nginx.org security advisory rates CVE-2026-123007 as \"major\". Wiz, which documented the whole set, scores CVE-2026-123007 and CVE-2026-123633 at 9.2 on CVSS 4.0, which is \"critical\", and describes unauthenticated remote code execution.\n\nThree nuances matter for the decision. The attack requires HTTP\u002F2 to be enabled. CVE-2026-123007, an integer underflow on the HTTP\u002F2 send window, is exploitable with the default configuration as soon as HTTP\u002F2 is on: Wiz demonstrated it on a 64-bit system serving static files. Exploitation remains difficult, since it needs a memory leak and then heap grooming, but ASLR does not protect you. Finally, we have not established that a public exploit exists; that is no reason to wait.",{"type":41,"title":42,"headers":43,"rows":47},"comparison","The HTTP\u002F2 flaws and their neighbors: affected and fixed versions",[44,45,46],"Flaw or product","Affected versions","Fixed in",[48,52,55,58,61,64,68],[49,50,51],"CVE-2026-123007 — memory corruption, HTTP\u002F2 flow control (major)","1.9.5 to 1.31.8","1.30.7 and 1.31.9",[53,54,51],"CVE-2026-123633 — HTTP\u002F2 use-after-free (medium at nginx.org, 9.2 at Wiz)","1.19.7 to 1.31.8",[56,57,51],"CVE-2026-123634 — resolver (medium)","0.6.18 to 1.31.8",[59,60,51],"CVE-2026-121810 — HTTP\u002F3 (medium)","1.25.0 to 1.31.8",[62,63,51],"CVE-2026-113425 — mail proxy module (major)","0.5.33 to 1.31.8",[65,66,67],"CVE-2026-125283 — try_files and alias","Range to read in the nginx.org advisory","1.30.7 (CHANGES-1.30)",[69,70,71],"NGINX Plus — CVE-2026-123007","See the vendor advisory","37.0.8.1 and 37.3.0.1 (according to Wiz)",{"type":37,"title":73,"body":74},"Am I exposed? Four checks per server","A server is exposed when two conditions add up: HTTP\u002F2 is enabled on at least one reachable `server`, and the running nginx process does not include the fix. The second condition is the one people miss: the binary installed on disk and the binary executing in memory are not necessarily the same.\n\nA word on Cloudflare and other CDNs or WAFs. According to Wiz, a service that terminates HTTP\u002F2 in front of your server may partially mitigate the attack. But if the origin IP is still directly reachable, the origin remains exposed: do not treat this mitigation as protection, and fix the server.",{"type":76,"title":77,"steps":78},"steps","Check one server in ten minutes",[79,82,85,88,91,94],{"title":80,"body":81},"Note the version and where it comes from","`nginx -v` gives the version of the binary on disk. `nginx -V 2>&1 | head -3` adds the build options. The origin decides the procedure: `apt-cache policy nginx` on Debian or Ubuntu, `rpm -qi nginx | grep -E 'Version|Release|Vendor'` on RHEL and derivatives. An old version number is not conclusive: see distribution packages below.",{"title":83,"body":84},"Find out which version is really running","`ps -o lstart= -p $(cat \u002Frun\u002Fnginx.pid)` gives the start time of the master process. Compare it with the date of the last package update: `grep ' upgrade nginx' \u002Fvar\u002Flog\u002Fdpkg.log | tail -3` on Debian or Ubuntu, `rpm -q --last nginx` on RHEL. `sudo ls -l \u002Fproc\u002F$(cat \u002Frun\u002Fnginx.pid)\u002Fexe` shows `(deleted)` if the master runs a binary that has since been replaced. Adjust the PID file path if needed.",{"title":86,"body":87},"Look for HTTP\u002F2 in the effective configuration","`sudo nginx -T 2>\u002Fdev\u002Fnull | grep -n 'listen.*http2\\|http2 on'`\n`nginx -T` tests then prints the full configuration, included files too. Before nginx 1.25.1, HTTP\u002F2 is enabled only through the `http2` parameter of `listen`. Since 1.25.1, the `http2 on;` directive exists too, at `http` or `server` level. No line: HTTP\u002F2 is not declared.",{"title":89,"body":90},"Check from the outside, name by name","`curl -sI --http2 https:\u002F\u002Fyour-domain.com | head -1`\n`HTTP\u002F2 200` means HTTP\u002F2 is negotiated; `HTTP\u002F1.1 200` means it is not. Repeat the test for each name served: sites sharing the same port can have different settings.",{"title":92,"body":93},"Look at the neighboring modules","`nginx -V 2>&1 | grep -o 'with-mail\\|http_v3'`\nWithout `--with-mail`, the mail proxy module (CVE-2026-113425) is not compiled. Without `--with-http_v3_module`, CVE-2026-121810 does not concern you. Write down the result next to the two previous checks.",{"title":95,"body":96},"Classify the server","Exposed: HTTP\u002F2 enabled and an unfixed version, or an old binary still in memory. To plan within the week: HTTP\u002F2 off but a version in the affected range. Not concerned: fixed package and process restarted after the update. Keep this table per client: it is the answer to give when a client asks whether they were affected.",{"type":37,"title":98,"body":99},"Fixed versions by distribution: nginx -v is not enough","This is the most common objection: `nginx -v` prints 1.22.1 or 1.26.3, far below 1.30.7, and yet the machine may be fixed. Distributions backport security fixes into their own branch without changing the upstream number: only the package suffix moves. The reliable criterion is therefore the full package number, read with `dpkg -s nginx | grep '^Version'` on Debian or Ubuntu, or `rpm -q nginx` on the RHEL family, compared with the table below.\n\nFor distributions whose status was not checked, read the distribution's errata or security tracker: `zgrep CVE-2026-123007 \u002Fusr\u002Fshare\u002Fdoc\u002Fnginx*\u002Fchangelog.Debian.gz` on Debian or Ubuntu, `rpm -q --changelog nginx | grep CVE-2026-123007` on the RHEL family. A matching line proves the fix is backported; no line proves it is not yet.",{"type":41,"title":101,"headers":102,"rows":106},"Fixed packages by distribution",[103,104,105],"Distribution","Fixed package","Reference",[107,111,115,119,123,126,129,132,136],[108,109,110],"Debian 12 (bookworm)","`1.22.1-9+deb12u11`","DLA-4918-1",[112,113,114],"Debian 13 (trixie)","`1.26.3-3+deb13u11`","DSA-6642-1",[116,117,118],"Debian forky","Not fixed; fix in sid, `1.30.6-4`","Debian security tracker",[120,121,122],"Ubuntu 26.04","`1.28.3-2ubuntu1.13`","Ubuntu security tracker",[124,125,122],"Ubuntu 24.04","`1.24.0-2ubuntu7.20`",[127,128,122],"Ubuntu 22.04","`1.18.0-6ubuntu14.23`",[130,131,122],"Ubuntu 20.04 (ESM)","`1.18.0-0ubuntu1.7+esm5`",[133,134,135],"AlmaLinux, Rocky, RHEL","Status not verified: read the distribution errata","Distribution errata",[137,138,139],"nginx.org repository","1.30.7 (stable) or 1.31.9 (mainline)","nginx.org security advisories",{"type":37,"title":141,"body":142},"\"I ran nginx -s reload\": no, that is not enough","`nginx -s reload` and `systemctl reload nginx` send a signal to the master process, which rereads the configuration and replaces the workers. The master, however, remains the same process, started from the old executable. After a package update, a reload therefore leaves the old code in memory: that is what the `(deleted)` mention in front of `\u002Fproc\u002F\u003Cpid>\u002Fexe` shows.\n\nTo load the new binary, there are two routes. Restarting the service is the simplest and cuts connections for a few seconds. Hot replacement of the binary with the `USR2` signal, described in the nginx documentation, avoids that cut but requires a good knowledge of your systemd setup. In both cases, you then check that the old processes are gone.",{"type":76,"title":144,"steps":145},"Fix, restart, check",[146,149,152,155,158,161],{"title":147,"body":148},"Test the configuration first","`sudo nginx -t`\nThe expected answer contains `syntax is ok` and `test is successful`. An invalid configuration leaves the service stopped after a restart.",{"title":150,"body":151},"Update the package","`sudo apt update && sudo apt install --only-upgrade nginx` on Debian or Ubuntu, `sudo dnf upgrade nginx` on the RHEL family. Then read the package version and compare it with the table: `dpkg -s nginx | grep '^Version'`.",{"title":153,"body":154},"Restart, do not reload","`sudo systemctl restart nginx`\nThe interruption lasts a few seconds. Pick a quiet slot for production servers.",{"title":156,"body":157},"Variant without interruption: hot replacement","`sudo kill -USR2 $(cat \u002Frun\u002Fnginx.pid)` starts a new master with the new binary. Then `sudo kill -WINCH $(cat \u002Frun\u002Fnginx.pid.oldbin)` stops the old master's workers, and `sudo kill -QUIT $(cat \u002Frun\u002Fnginx.pid.oldbin)` stops the old master. After each signal, check that the site still answers.",{"title":159,"body":160},"Check that the old processes are gone","`pgrep -a nginx` must list only recent processes. `ps -o lstart= -p $(cat \u002Frun\u002Fnginx.pid)` must give a date later than the package update. `sudo ls -l \u002Fproc\u002F$(cat \u002Frun\u002Fnginx.pid)\u002Fexe` must no longer show `(deleted)`.",{"title":162,"body":163},"Check the service and HTTP\u002F2 negotiation","`curl -sI --http2 https:\u002F\u002Fyour-domain.com | head -1` confirms the site answers. Note the date and the version in your fleet table, then move to the next server.",{"type":37,"title":165,"body":166},"Docker and Nginx Proxy Manager: the image carries its own nginx","In a container, the nginx concerned is the one in the image, never the host's. Check it with `docker exec \u003Ccontainer> nginx -v`. To fix it, pull or rebuild the image, then recreate the container: `docker compose pull && docker compose up -d --force-recreate`, or `docker compose build --pull && docker compose up -d` for an image built with `FROM nginx:…`. A bare `docker restart` keeps the old image.\n\nNginx Proxy Manager ships its own nginx. At the time of writing, the image we looked at contained nginx 1.31.8, an affected version. We have not established that a fixed image is already published: check the version inside the container with `docker exec \u003Ccontainer> nginx -v`, and do not wait to act on HTTP\u002F2. In the meantime, turn off the HTTP\u002F2 setting of each proxy host, in its SSL tab. Our guide \u003Ca href=\"\u002Fblog\u002Fdeployer-avec-nginx-proxy-manager\">Nginx Proxy Manager on a VPS\u003C\u002Fa> reminds you how it is deployed.",{"type":168,"title":169,"body":170},"tip","Workaround until you update: turn HTTP\u002F2 off","On nginx 1.25.1 or newer, add `http2 off;` in each `server` block. On all versions, remove the `http2` parameter from the `listen` directive: `listen 443 ssl http2;` becomes `listen 443 ssl;`. Then `sudo nginx -t` and `sudo systemctl reload nginx`: here a reload is enough, since only the configuration changes. Check with `curl -sI --http2 https:\u002F\u002Fyour-domain.com | head -1`, which must answer `HTTP\u002F1.1`. The cost is a slight performance drop on pages with many resources. This is a stopgap: it does not replace the update, and it does not cover the HTTP\u002F3 or mail proxy flaws.",{"type":37,"title":172,"body":173},"Detection: look for traces without concluding too fast","Wiz points to three indicators. The first is worker crashes: `grep -c 'exited on signal' \u002Fvar\u002Flog\u002Fnginx\u002Ferror.log` counts lines such as `worker process 12345 exited on signal 11`. Compare with previous weeks, and also read `journalctl -u nginx --since '7 days ago'`.\n\nThe second is unexpected child processes: `pstree -ap $(cat \u002Frun\u002Fnginx.pid)` should show under the master only `nginx: worker process` entries and, if you use a cache, its manager. A shell or any tool launched by nginx is a strong signal. The third is long HTTP\u002F2 connections sending many WINDOW_UPDATE frames: nginx does not log them by default, so look for them in the logs of a proxy or a network tool.\n\nThese traces are indicators, not proof, and their absence does not prove the server is clean. On a server you doubt, keep the logs before rotating them, then decide with the client whether TLS keys and certificates must be changed.",{"type":37,"title":175,"body":176},"Troubleshooting: the errors that follow the update","**`nginx: [emerg] unknown directive \"http2\"`.** You wrote `http2 on;` on a version older than 1.25.1, where the directive does not exist. Fix: update nginx, or drive HTTP\u002F2 through the `http2` parameter of `listen` (present to enable it, removed to disable it).\n\n**`nginx -t` succeeds, but the old binary is running.** `nginx -t` tests the new binary and the configuration on disk, not the master process already started. Fix: restart, then check that `(deleted)` no longer appears in `ls -l \u002Fproc\u002F\u003Cpid>\u002Fexe`.\n\n**`apt` keeps the old version.** An `apt-mark hold nginx` or a file in `\u002Fetc\u002Fapt\u002Fpreferences.d\u002F` freezes the package. Fix: `apt-mark showhold`, then `sudo apt-mark unhold nginx`. If nothing blocks it, the distribution may not have published its fixed package: see the table, and apply the workaround.\n\n**The container still answers with the old version.** The image is cached or the tag is pinned. Fix: `docker compose pull`, `docker compose up -d --force-recreate`, then `docker exec \u003Ccontainer> nginx -v`.\n\n**`nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)`.** An old master stayed alive after an interrupted hot replacement. Fix: `pgrep -a nginx`, stop the old master with `sudo kill -QUIT $(cat \u002Frun\u002Fnginx.pid.oldbin)`, then restart.",{"type":37,"title":178,"body":179},"Dozens of servers, one fix: the agency workload","For an agency, this fix is not one command, it is a tour of the fleet: one server per client, different origins (a Debian package here, the nginx.org repository there, a Docker image elsewhere), configurations written by several people. Each machine needs the inventory, the update, the restart, the check, then the answer to the worried client. Our guide on the October nginx configuration audit covers another wave, on the configuration side. If PHP is also in your fleet, see the PHP guide: the same tour is to be planned.\n\nThe most durable way to reduce this workload is to reduce the number of web servers you administer yourself. With ServOrbit.com reseller hosting, your clients' sites run in cPanel accounts that you manage from WHM, white-label: you keep the client relationship and your prices, we run the infrastructure. For machines that must stay under root access, the administration option is offered on our \u003Ca href=\"\u002Fvps-cloud\">VPS Cloud\u003C\u002Fa>.",{"type":37,"title":181,"body":182},"Official documentation","\u003Ca href=\"https:\u002F\u002Fnginx.org\u002Fen\u002Fsecurity_advisories.html\">nginx security advisories\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fnginx.org\u002Fen\u002FCHANGES-1.30\">CHANGES-1.30\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fwww.wiz.io\u002Fblog\u002Fnginx-http2-rce-vulnerabilities\">Wiz — nginx HTTP\u002F2 RCE vulnerabilities\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fsecurity-tracker.debian.org\u002Ftracker\u002FCVE-2026-123007\">Debian — CVE-2026-123007\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Fubuntu.com\u002Fsecurity\u002FCVE-2026-123007\">Ubuntu — CVE-2026-123007\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fnginx.org\u002Fen\u002Fdocs\u002Fcontrol.html\">Controlling nginx\u003C\u002Fa> · \u003Ca href=\"https:\u002F\u002Fnginx.org\u002Fen\u002Fdocs\u002Fhttp\u002Fngx_http_v2_module.html\">ngx_http_v2_module\u003C\u002Fa>","Fewer web servers to patch yourself","With ServOrbit.com reseller hosting, your clients' sites run under your brand, on infrastructure we operate. You keep the client relationship and your prices; we keep the server layer.","Explore the agency offer","\u002Fsolutions\u002Fagences",[188,205,225],{"id":189,"slug":190,"slugs":191,"title":195,"excerpt":196,"readTime":197,"views":198,"isPinned":19,"noindex":19,"publishedAt":199,"updatedAt":200,"category":201,"categories":202,"featuredImage":30,"bgImage":31,"posterImage":204,"relatedSolution":30},492,"nginx-cve-2026-15176-audit-and-patch-to-1-30-6",{"fr":192,"en":190,"ar":193,"es":194},"nginx-cve-2026-15176-mettre-a-jour","ثغرة-nginx-cve-2026-15176-الفحص-والتحديث-إلى-1-30-6","nginx-cve-2026-15176-auditar-y-actualizar-a-1-30-6","nginx CVE-2026-15176: audit and patch to 1.30.6","nginx 1.30.6 and 1.31.7 fix five flaws, including CVE-2026-15176. Affected versions, config audit commands, updates per system and mitigations.",12,2,"2026-10-22T00:00:00+00:00","2026-11-08T01:13:14+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[203],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fnginx-cve-2026-15176-mettre-a-jour-poster.svg",{"id":206,"slug":207,"slugs":208,"title":212,"excerpt":213,"readTime":214,"views":215,"isPinned":19,"noindex":19,"publishedAt":216,"updatedAt":200,"category":217,"categories":222,"featuredImage":30,"bgImage":31,"posterImage":224,"relatedSolution":30},37,"deploy-your-applications-with-nginx-proxy-manager-on-a-vps",{"fr":209,"en":207,"ar":210,"es":211},"deployer-avec-nginx-proxy-manager","انشر-تطبيقاتك-باستخدام-nginx-proxy-manager-على-خادم-vps","desplegar-con-nginx-proxy-manager","Deploy your applications with Nginx Proxy Manager on a VPS","Manage domains, SSL and reverse proxy for several services on a VPS with Nginx Proxy Manager: installation, Docker networks, 502 troubleshooting and configuration.",10,7,"2026-05-14T00:00:00+00:00",{"id":218,"name":219,"slug":220,"color":221,"icon":220},3,"Deployment","deploiement","bg-success\u002F10 text-success",[223],{"id":218,"name":219,"slug":220,"color":221,"icon":220},"\u002Fblog\u002Fcovers\u002Fdeployer-avec-nginx-proxy-manager-poster.svg",{"id":226,"slug":227,"slugs":228,"title":232,"excerpt":233,"readTime":234,"views":198,"isPinned":19,"noindex":19,"publishedAt":199,"updatedAt":235,"category":236,"categories":237,"featuredImage":30,"bgImage":31,"posterImage":239,"relatedSolution":30},489,"php2shell-cve-2026-109618-109619-patch-php",{"fr":229,"en":227,"ar":230,"es":231},"php2shell-cve-2026-109618-109619-mettre-a-jour-php","php2shell-cve-2026-109618-109619-تحديث-php","php2shell-cve-2026-109618-109619-actualizar-php","PHP2Shell: patch CVE-2026-109618 and CVE-2026-109619","PHP2Shell: two critical PHP flaws exploitable without an account. Patched versions, update commands per system and temporary mitigations.",16,"2026-11-08T01:13:15+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[238],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fphp2shell-cve-2026-109618-109619-mettre-a-jour-php-poster.svg",true,1795272629797]