
nginxの脆弱性対応に伴い、現在、緊急システムメンテナンスを実施しております。 ■完了予定:11月19日 20:00 ■対象CVE CVE-2026-123007 CVE-2026-123633 CVE-2026-123634 CVE-2026-121810 CVE-2026-113425 メンテナンス中、数秒程度Webサイトへ接続できない場合があります。 ご不便をおかけいたしますが、ご理解とご協力のほどお願いいたします。 詳細はリプライ欄のページをご確認ください。
Signal is active with 4 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
7 versions affected across 7 products

nginxの脆弱性対応に伴い、現在、緊急システムメンテナンスを実施しております。 ■完了予定:11月19日 20:00 ■対象CVE CVE-2026-123007 CVE-2026-123633 CVE-2026-123634 CVE-2026-121810 CVE-2026-113425 メンテナンス中、数秒程度Webサイトへ接続できない場合があります。 ご不便をおかけいたしますが、ご理解とご協力のほどお願いいたします。 詳細はリプライ欄のページをご確認ください。

🚨 Five vulnerabilities in nginx, nicknamed NGINX2Root, were disclosed by nginx today: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-113425, and CVE-2026-121810. Due to the severity, patches went straight to production repos. Update ASAP! https://almalinux.org/blog/2026-11-18-nginx2root/?utm_medium=social&utm_source=twitter

🚨 NGINX'te 5 Güvenlik Açığı: Pre-Auth RCE ve Linux Kernel Açığıyla ROOT Yetkisine Yükselme Riski! NGINX için beş farklı güvenlik açığı (CVE) duyuruldu ve yeni sürümlerde yamalandı. Ayrıca, bir Linux kernel açığıyla birleştirilen exploit zinciri üzerinden root yetkisine ulaşılabildiği iddia ediliyor. HTTP/2 kaynaklı iki kritik açık, kimlik doğrulaması gerektirmeden uzaktan kod çalıştırılmasına (Pre-Auth RCE) imkan tanıyor. Açıkların istismar koşulları yapılandırmaya göre değişiyor. 🔴 Tespit edilen CVE'ler: • CVE-2026-123007 — HTTP/2 • CVE-2026-123634 — Resolver • CVE-2026-123633 — HTTP/2 • CVE-2026-121810 — HTTP/3 • CVE-2026-113425 — Mail Proxy Bunlara ek olarak CVE-2026-118899, TLS 1.3 üzerinden istek gövdesi okunurken NGINX worker process'inin sonsuz döngüye girerek hizmet dışı kalmasına (DoS) neden olabiliyor. Bu açık için de yama yayınlandı. 📌 NGINX Open Source için yamalanmış sürümler: • Stable: 1.30.7 • Mainline: 1.31.9 Sunucularınızın sürümünü ve yapılandırmasını kontrol edin, güncellemeleri geciktirmeyin!

👁️Los que no mucho te dicen es que #nginx vulnerable con CVE-2026-123634 significa F5 vulnerable si tienes NGINX Plus/Open Source configurado como proxy (o sea...) Info: https://blog.segu-info.com.ar/2026/11/siete-vulnerabilidades-criticas-en-nginx.html

🚨 NGINX2ROOT FOLLOW-UP: FIVE NGINX RCE PATHS, PLUS A CHAIN TO HOST ROOT Follow-up to our earlier NGINX2Root post: Xint's full write-up is out, and it adds detail beyond CVE-2026-123007. What's new: • Five independent flaws, each a separate attack path depending on configuration: CVE-2026-123007 (HTTP/2), CVE-2026-123633 (HTTP/2 with an upstream), CVE-2026-121810 (HTTP/3 with an upstream), CVE-2026-123634 (resolver, request-derived proxy_pass and mirror) and CVE-2026-113425 (mail proxy with auth_http) • Disabling HTTP/2 blocks only two of the five, so it is not a full workaround • Xint chained an nginx worker RCE with a Linux kernel SCTP flaw to get root on the host, including out of a Docker container. Xint is withholding kernel exploit details until a patch exists, and says hosts that don't use SCTP can block the module from loading • Xint says its exploit worked on AWS, GCP and Azure targets, including over a public HTTPS endpoint • Exposure: per Xint's Shodan check on Nov 10, 98.9% of nginx hosts reporting a version fall in the CVE-2026-123007 range (1.9.5-1.31.8). Version strings can be misleading, and distro packages may carry backported fixes Fix: NGINX Open Source 1.30.7 (stable) or 1.31.9 (mainline). Restart nginx or do a live binary upgrade, because a config reload alone does not replace the running executable. ⚠️ Analyst Note: The nginx flaws give code execution as the worker account, not root by themselves. The root step needs the separate kernel bug. We have seen no report of exploitation in the wild so far, but multiple teams have working exploits, so prioritize internet-facing nginx. https://nginx2root.com/ #DDW #NGINX #nginx2root #CVE2026123007 #RCE #ThreatIntelligence #CyberSecurity

🚨 GoPlus Security Alert: Five nginx2root Vulnerabilities Disclosed—Check HTTP/2-Enabled Deployments First On November 18, NGINX released security updates addressing five nginx2root vulnerabilities, including CVE-2026-123007. These are independent attack paths affecting different configurations. Successful exploitation allows arbitrary code execution with the privileges of an nginx worker process. The demonstrated attack chain achieves root access on the host by chaining a separate Linux kernel privilege escalation vulnerability. https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities 📌 Exploitation Conditions All five vulnerabilities can be exploited without authentication when their respective version and configuration requirements are met. 1. CVE-2026-123007 (broadest exposure): An unpatched nginx build includes the HTTP/2 module, with HTTP/2 enabled on a listener reachable by the attacker. The officially affected versions are 1.9.5–1.31.8. Version numbers alone do not establish exposure—check the actual build, active configuration, and whether the distribution has backported a fix. 2. CVE-2026-123634: A resolver is configured, the proxy_pass destination is derived from request data, and mirror is used with mirror_request_body off. 3. CVE-2026-123633: nginx receives requests over HTTP/2 and proxies them to an upstream server while available connection slots in the worker are running low. 4. CVE-2026-121810: HTTP/3 is enabled, and requests are reverse-proxied to an upstream server. 5. CVE-2026-113425: The nginx mail proxy is enabled with both proxy on and auth_http configured. 🛡️ Security Recommendations 1. Prioritize internet-facing nginx instances with HTTP/2 enabled, then check the configuration requirements for the remaining vulnerabilities. 2. Upgrade NGINX Open Source 1.31 deployments to 1.31.9 or later, and 1.30 deployments to 1.30.7 or later. For NGINX Plus or distribution packages, consult the relevant vendor advisories to confirm patched releases and backported fixes. 3. If you cannot upgrade immediately, temporarily disable HTTP/2 on affected listeners. Apply the configuration change and confirm that the old worker processes have exited. This mitigates only the two HTTP/2 attack paths. After installing the patched binary, restart nginx or perform a supported live binary upgrade. Reloading the configuration alone does not replace the running binary.

NGINX2Root: five NGINX flaws led by CVE-2026-123007 can give an unauthenticated attacker code execution via HTTP/2, HTTP/3, the DNS resolver or the mail proxy. Public PoC exists, no in-the-wild exploitation reported yet. - Scope: Xint (Theori) reported all five on October 16, 2026, and F5 shipped fixes on November 18, 2026, the day of disclosure. F5 scores each 9.2 Critical under CVSS v4.0 and 8.1 High under CVSS v3.1. Affected: NGINX Open Source before 1.30.7 and 1.31.9, and NGINX Plus before 37.0.8.1 and 37.3.0.1. Plus R33 through R36 have no patch, so those customers must move to a 37.x build. - Config decides exposure: CVE-2026-123007 is the broadest, a send-window miscount in HTTP/2 flow control that corrupts memory and needs only HTTP/2 on a reachable listener. CVE-2026-123633 (HTTP/2) and CVE-2026-121810 (HTTP/3) are use-after-free bugs in connection draining with proxying to a backend. CVE-2026-123634 is a resolver use-after-free needing a request-derived proxy_pass target plus SSI or mirror subrequests. CVE-2026-113425 hits the mail proxy when proxy and auth_http are combined. - Root chain: code execution lands as the NGINX worker, then a separate Linux kernel SCTP use-after-free or double free (code introduced in Linux 4.15) escalates to root. The researchers say the chain also crossed a Docker container boundary. That kernel bug has no CVE and no fix yet. ATT&CK per the report: T1190, T1068, T1611. - Exploit reality: the public PoC for CVE-2026-123007 (GitHub, November 18) gets code execution against NGINX 1.31.8 with HTTP/2 over TLS in a Docker lab. It needs x86-64 with AVX-512 and a particular glibc memory-copy routine, has to defeat ASLR, and pushes roughly 128 GB of HTTP/2 traffic down a single connection. A proxy terminating HTTP/2 in front of NGINX will most likely stop it. The discoverers and another team hold working exploits but withheld the final steps. Fake exploit repos are circulating, so vet anything you pull. - Evidence to look for: worker crashes and core dumps (grep 'exited on signal' /var/log/nginx/error.log), an HTTP/2 connection open for minutes ingesting large volumes while the access log shows few requests, a worker spawning a shell or other program, and outbound connections or DNS lookups the host does not normally make. The warning signs come from CIRCL's advisory; the grep is from the report's checks. Takeaway: scope first, then fix. Run nginx -v and match against your distro advisory, since backports keep old version numbers (Ubuntu shipped fixes November 19). Run nginx -T 2>/dev/null | grep -nE 'http2|http3|quic|resolver|proxy_pass|mirror|ssi on|auth_http' to see which flaws apply. Check bundled NGINX in container images, appliances and load balancers. Community ingress-nginx is retired with no fix planned. After upgrading, do a full restart, because a reload keeps the old binary running. If patching waits, disable the feature behind each flaw. Turning off HTTP/2 covers only CVE-2026-123007 and CVE-2026-123633, and disabling mirror alone leaves CVE-2026-123634 open. On hosts that do not need SCTP, add install sctp /bin/false under /etc/modprobe.d/ and confirm with lsmod, since an already-loaded module stays active until reboot or removal. Check sysctl kernel.randomize_va_space (2 is full) and look for services launched with setarch -R. Preserve error logs and worker core dumps before restarting.

🚨 Another critical security alert for production infrastructure! After the recent OpenJDK Java4Shell vulnerability, NGINX now has five critical RCE vulnerabilities. They are collectively being called NGINX2Root. Five CVEs: - CVE-2026-123007 - CVE-2026-123633 - CVE-2026-121810 - CVE-2026-123634 - CVE-2026-113425 The scary part? Some of these can allow unauthenticated attackers to execute code on the server with NGINX worker privileges. Even static websites need to be assessed. What should you do? → Stable: Upgrade to NGINX 1.30.7 → Mainline: Upgrade to NGINX 1.31.9 → Check HTTP/2 and HTTP/3 configuration → Review reverse proxy and mail proxy configurations → Rebuild Docker images and redeploy Don't just patch your application dependencies. Your infrastructure needs security updates too. Check your NGINX version today. Official advisory: https://nginx.org/en/security_advisories.html

【2026-11-19】NGINX2Root / NGINX2Shell:HTTP/2フロー制御の整数アンダーフローで認証不要RCE(CVE-2026-123007ほか)、公開PoCあり・AI発見が複数チームで同時発生 日本語圏(Yahoo!ニュース、Zenn、Qiita、はてなブックマーク、Yahoo!リアルタイム検索など)を横断確認したところ、2026-11-19朝時点でビジネス+ITのニュース記事や一部のZenn投稿で概要が触れられているものの、一次情報の突き合わせ・PoCの制約条件・AI発見の文脈を含めた詳細な技術解説はまだ限定的だった。海外ではWiz Research、Rapid7、Xint(Theori)、Ikotas Labs、Metnirが独立して報告し、F5が同日にパッチを出した。一次情報はnginx公式アドバイザリ、各社ブログ、Rapid7の公開PoCリポジトリ、Xintの開示を確認した。 ■ 背景 nginxは世界で最も広く使われるオープンソースWebサーバー/リバースプロキシの一つで、公式主張では2億2500万以上のサイトを支えている。2026年11月18日、F5(nginxメンテナ)は安定版1.30.7とmainline 1.31.9を緊急リリースし、10件前後の脆弱性を修正した。その中核が「nginx2root」(Xint命名)または「NGINX2Shell」と呼ばれる一連のメモリ安全性問題で、特にCVE-2026-123007はHTTP/2のフロー制御に2015年の1.9.5から存在していた整数アンダーフローだ。 複数のセキュリティチームが独立して(多くがAI支援のコード解析を利用)同じ系統のバグを発見した点が特徴的で、PHP2Shellに続く「基盤ソフトウェアへのAI発見」の流れを示している。 ■ 仕組みの要点 主要なものは以下(nginx公式のseverityと研究者側のCVSS 4.0評価に乖離あり): - **CVE-2026-123007**(HTTP/2フロー制御メモリ破壊、nginx公式「major」、研究者側CVSS 4.0 9.2):`send_window`の管理で、ストリームキャンセル時に未送信データを上限チェックなしに加算。WINDOW_UPDATEフレームを大量に送り続けると整数アンダーフローし、TLS送信パス(`ngx_ssl_send_chain`など)で範囲外メモリコピーが発生。静的ファイル配信のみでも成立し、HTTP/2が有効なだけで影響。Wizは公式ビルド1.31.7/1.31.8でASLRバイパスを含むRCEを確認。影響範囲:1.9.5〜1.31.8。 - **CVE-2026-123633**(HTTP/2 use-after-free、公式「medium」):接続スロットが不足した状態でプロキシ処理中に接続を閉じると発生。upstream(proxy_passなど)が必要。 - その他:CVE-2026-121810(HTTP/3 UAF)、CVE-2026-123634(resolver + mirror関連UAF)、CVE-2026-113425(mail proxy UAF、広範)など。合計で複数の独立したRCE経路。 XintはこれらをLinuxカーネルのSCTP関連use-after-free(2018年の4.15由来、当時未パッチ)とチェーンし、nginx worker権限からホストrootまで到達する実証を報告(Docker内からも)。詳細の多くは非公開。 修正は小さな差分で対応(公式コミットでWINDOW_UPDATEのキューフレーム考慮など)。 ■ 結果・公開PoCの実態 Rapid7のStephen FewerがGitHubに公開PoC(sfewer-r7/CVE-2026-123007)を出した。Docker上の1.31.8(HTTP/2+TLS)でRCEを示すが、制約が厳しい: - 単一コネクションで約128GBのHTTP/2トラフィック(WINDOW_UPDATE中心)。10Gbit/sで約2分、1Gbit/sで約17分。300Mbit/s以下ではデフォルトのkeepalive_time(1時間)で途切れる可能性。 - AVX-512対応CPU上の特定のglibc memcpy高速パスに依存。 - フレッシュなヒープや低負荷環境で成功しやすく、プロキシ経由や高負荷本番では成立しにくい。 - 検出シグナルとして大量のWINDOW_UPDATEや特定のTLS KeyUpdateが有用。 WizやXintは自前のエクスプロイトを非公開。Censysなどはより軽量な状態確認用テストを公開。2026-11-18時点でin-the-wildの悪用報告はなく、CISA KEV未収載。ただし公開PoCが出た以上、スキャンや試行は急速に増える可能性が高い。 ■ 実務的な影響とバランスの取れた評価 **長所(対応の容易さ)**: - 修正版が即日公開。`http2 off;`で当該HTTP/2系は緩和可能(他のCVEは残る)。 - 多くの環境ではCDN/WAF/ロードバランサでHTTP/2を終端しているため、オリジンnginxに直接届きにくい。 - PoCが「うるさい」(大容量トラフィック)ため、検出やレート制限で防ぎやすい側面もある。 **注意点**: - 2015年から存在するバグで、広範なバージョンが影響。ディストリビューションのバックポートや古いコンテナ・アプライアンスは要確認。 - NGINX Plusの一部古いリリース(R34-R36など)は修正なしの報告あり。 - AIによる発見が加速しており、基盤ソフトウェアの「隠れた長期バグ」が今後も短期間で表面化するリスク。 - ワーカー権限でも、TLSキーやセッション情報の読み取り、横展開の起点になりうる。Rootlessコンテナや読み取り専用ファイルシステムは被害限定に有効。 実務上の優先順位:公開インターネットに直接HTTP/2を晒しているnginxを最優先で1.30.7/1.31.9(またはベンダーパッチ)へ更新・再起動。設定でHTTP/2を切れるなら暫定対応。ログで異常な大量WINDOW_UPDATEやworkerクラッシュ(signal 11)を監視。 出典: - nginx security advisories / changelog(1.31.9 / 1.30.7) - Wiz Research: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities - Rapid7 blogおよびGitHub PoC - Xint: nginx2root開示 - 各社(JFrog、Qualys、Cyber Kendraなど)の分析 -2026-123007 セキュリティ 脆弱性発見 (一次情報を確認し、日本語圏での詳細な技術解説がまだ薄い段階でまとめています。数値・条件は各公開報告に基づく。PoCの実行再現は行っていません。)

English is below 【重要】 kusanagi-nginxを更新しました。 複数の脆弱性(CVE-2026-125283, CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, CVE-2026-113425, CVE-2026-120967, CVE-2026-120993, CVE-2026-123640, CVE-2026-118899)への対応が含まれているため、nginxご利用の方はアップデートをお願いします。 kusanagi-nginx131 モジュール更新情報 1.31.9-1 https://kusanagi.tokyo/releases/28499/ kusanagi-nginx131 モジュール更新情報 1.31.9-1.el9 https://kusanagi.tokyo/releases/28493/ 合わせてSecurity Advisoryも公開しました 緊急: kusanagi-nginx131 脆弱性情報 https://kusanagi.tokyo/releases/28497/ 緊急: kusanagi-nginx130 脆弱性情報 https://kusanagi.tokyo/releases/28474/ [Important] kusanagi-nginx has been updated. Multiple vulnerabilities (CVE-2026-125283, CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634, CVE-2026-113425, CVE-2026-120967, CVE-2026-120993, CVE-2026-123640, CVE-2026-118899) . If you are using nginx, please update it. kusanagi-nginx131 Module Update 1.31.9-1 https://kusanagi.tokyo/en/releases/28500/ kusanagi-nginx131 Module Update 1.31.9-1.el9 https://kusanagi.tokyo/en/releases/28494/ We have also published a security advisory. Critical: kusanagi-nginx130 Security Update https://kusanagi.tokyo/en/releases/28475/ Critical: kusanagi-nginx131 Security Update https://kusanagi.tokyo/en/releases/28498/

nginxの脆弱性(NGINX2Root / NGINX2Shell: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425)と修正バージョ>ン(1.31.9/1.30.7) #sios_tech #security #vulnerability #セキュリティ #脆弱性 #nginx #nginx2root #nginx2shell https://security.sios.jp/vulnerability/nginx-security-vulnerability-20261119/

NGINX2Root: From nginx visitor to root of the server host CVE-2026-123007 CVE-2026-123634 CVE-2026-123633 CVE-2026-121810 CVE-2026-113425 https://nginx2root.com/

nginx-1.30.7 stable and nginx-1.31.9 mainline versions have been released, with vulnerability fixes for use-after-free in resolver (CVE-2026-123634), memory corruption in HTTP/2 flow control (CVE-2026-123007), use-after-free in HTTP/3 (CVE-2026-121810), use-after-free in HTTP/2 (CVE-2026-123633), infinite loop while reading client request body over TLS 1.3 (CVE-2026-118899), use-after-free in mail proxy module (CVE-2026-113425), NULL pointer dereference when using PROXY protocol version 2 (CVE-2026-120993), buffer overflow when using alias with try_files (CVE-2026-125283), SNI bypass in client certificate validation in stream module (CVE-2026-120967), and insufficient validation in stream ssl_preread module (CVE-2026-123640).

nginx2root: five unauthenticated memory corruption bugs in nginx, plus a Linux kernel SCTP flaw that turns a worker foothold into root. CVE-2026-123007 (HTTP/2, present since 1.9.5 in 2015) is the worst. Not in CISA KEV as of Nov 19. - The five CVEs: CVE-2026-123007 is an integer overflow leading to out-of-bounds heap read/write, needing only HTTP/2. CVE-2026-123633 is a use-after-free (HTTP/2, proxy_pass, worker low on worker_connections). CVE-2026-121810 is a use-after-free in HTTP/3 (QUIC) with proxy_pass. CVE-2026-123634 is a use-after-free in the resolver with variable proxy_pass plus a mirror or SSI subrequest. CVE-2026-113425 is a use-after-free in the mail proxy with auth_http. F5 rates each High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2). Code execution needs ASLR disabled or bypassed, and Xint's write-up shows CVE-2026-123007 leaking addresses to do that. - How CVE-2026-123007 works: the WINDOW_UPDATE handler caps the connection send window at 2^31 - 1. But ngx_http_v2_filter_cleanup() refunds credit for queued DATA frames on a canceled stream with no cap. If the client enlarges the window between queueing and cancel, the window exceeds the max, the unsigned check wraps, and every later WINDOW_UPDATE is accepted. Past 2^63 the signed comparison in ngx_http_v2_send_chain() produces a huge frame size and a buffer with last before pos, reaching memcpy() in ngx_ssl_send_chain(). Xint, Rapid7 and Wiz report code execution. The fix adds h2c->send_queued so queued bytes count against the window. - The kernel half: Xint found a use-after-free in the Linux SCTP send path, present since 4.15 (2018). An attacker already running as the nginx worker can get root, demonstrated from inside a Docker container. Many distributions auto-load the SCTP module on first SCTP socket open, so hosts that never use SCTP can still be exposed. As of Nov 18 no kernel fix existed and Xint is withholding details. - Exploitation status: no reports of in-the-wild exploitation as of Nov 19. Rapid7 published a PoC meant only for a freshly started local container. Xint and Wiz have not released exploits, and fake exploits are circulating on GitHub. Censys's tracker counts about 8.8 million services running a potentially affected version with HTTP/2 enabled, though backported fixes mean version strings alone don't prove exposure. - What the evidence looks like: Rapid7 estimates reaching 2^63 takes roughly 2^32 WINDOW_UPDATE frames (about 52 GiB), and its route totals about 128 GB of HTTP/2 data. That means one long-lived connection delivering tens of GB to nginx while little comes back, far more than the logged requests explain. Other signals from the report: worker process <pid> exited on signal 11 (alert) alongside worker_connections are not enough, reusing connections (warn) on HTTP/2 or HTTP/3 proxy servers. The line could not cancel <name> resolving (alert) appears on unpatched versions for CVE-2026-123634, but its absence proves nothing. Mail proxy workers crashing with client resets during login point at CVE-2026-113425. The strongest sign of success is unexpected programs launched by an nginx worker, for example an auditd rule on execve for the worker's user. Takeaway: patch to nginx 1.30.7 or 1.31.9 (Plus 37.0.8.1 or 37.3.0.1, or your distro's fixed build) and restart, because a config reload does not replace the running binary. Check backports against the full package version. If you can't patch yet, set http2 off; (1.25.1+), remove QUIC listeners and set http3 off;, bind mail listeners to trusted networks, and add install sctp /bin/false under /etc/modprobe.d/ (this does not unload an already-loaded module). A front-end proxy like Cloudflare's, which terminates HTTP/2 and HTTP/3 and runs its own flow control, blocks the frame-level attacks, but only if the origin can't be hit directly, so enforce that with an IP firewall, not nginx config. It does not cover the mail proxy or fully cover the resolver bug. Note that the warn message above sits below the default error level, so raise error_log verbosity and preserve logs now. Diff inbound vs outbound bytes per HTTP/2 connection and pair signal 11 worker exits with execve audit events.

🚨 Nginx 爆出重大安全漏洞!NGINX2Root:5 个远程代码执行漏洞,甚至可能导致 Linux 主机失守。 11 月 18 日,Nginx 官方发布安全公告,披露并修复了 10 项安全问题,其中 5 个由安全研究团队 Xint 发现的漏洞被统称为 NGINX2Root。 最值得关注的是 CVE-2026-123007: CVSS 4.0:9.2 影响 HTTP/2 流量控制模块 影响未修复的 Nginx 1.9.5 至 1.31.8 无需身份认证 开启 HTTP/2 的目标可能遭受远程代码执行 另外还有 4 个漏洞: CVE-2026-123633:HTTP/2 Use-After-Free CVE-2026-123634:DNS Resolver Use-After-Free CVE-2026-121810:HTTP/3 Use-After-Free CVE-2026-113425:Mail Proxy Use-After-Free 真正可怕的是后续攻击链。 Xint 研究人员还发现了一个独立的 Linux 内核 SCTP 漏洞,可以与 Nginx 漏洞组合,实现从 Nginx Worker 权限提升到宿主机 Root。 研究人员甚至演示了从 Docker 容器逃逸,获取底层宿主机控制权。 ⚠️ 修复方案: Nginx 官方已经发布安全版本: Stable:1.30.7 Mainline:1.31.9 如果暂时无法升级,可以临时关闭 HTTP/2,但这只能缓解其中两个漏洞,不能替代完整补丁。 升级后还需要重启 Nginx,单纯 reload 不够。 值得注意的是,Linux 内核 SCTP 漏洞目前尚无公开 CVE 编号及修复补丁。 截至 11 月 19 日,尚无可靠公开报告证实这些漏洞已在野外遭到利用,但 CVE-2026-123007 的 PoC 已公开。 如果你有运行 Nginx 的 VPS、反向代理、网站或 Kubernetes 集群,建议尽快检查。 官方安全公告: https://nginx.org/en/security_advisories.html 研究团队完整技术报告: https://xint.io/blog/nginx2root-remote-code-execution

🚨 Nginx 史诗级漏洞预警:NGINX2Root 今天凌晨,Nginx 爆出潜伏 10 余年的高危漏洞链 NGINX2Root,共 5 个 CVE,CVSS 4.0 评分 9.2。 只要服务器对外开启了 HTTP/2,未经认证的攻击者就可能远程执行代码。配合 Linux 内核提权漏洞,还可进一步逃逸 Docker、拿下宿主机 root。 📌 核心漏洞 CVE-2026-123007(HTTP/2,最严重) CVE-2026-123633 / CVE-2026-123634 CVE-2026-121810 / CVE-2026-113425 📌 受影响版本 Nginx 1.9.5 ~ 1.31.8(HTTP/2 漏洞) 即自 2015 年引入 HTTP/2 以来的几乎所有版本 🔍 一秒自查 在终端运行: openssl s_client -connect 你的域名:443 -alpn h2 如果返回结果里出现 ALPN protocol: h2,说明已对外暴露 HTTP/2,在受影响范围内。 再顺手查一下 Nginx 的 error.log,如果近期出现莫名的 worker process exited on signal 异常退出记录,建议重点排查是否已被扫描试探。 🛠 修复方法 立即升级到修复版本,并重启 Nginx(只 reload 不够): 稳定版:1.30.7 主线版:1.31.9 暂时无法升级的,先关闭 HTTP/2 临时缓解: http2 off; 注意:关 HTTP/2 只能堵住两个 HTTP/2 漏洞,不能替代升级。 有线上服务的,今天就升级,别拖!! 来源:http://nginx.org 安全公告 / Xint NGINX2Root 披露 #Nginx #漏洞预警 #服务器安全

🚨GoPlus安全警报:nginx2root 多个漏洞披露,HTTP/2 服务需优先排查 11月18日,NGINX 发布安全更新,修复包括 CVE-2026-123007 在内的五个 nginx2root 漏洞。五个漏洞是相互独立的攻击路径,分别影响不同配置;成功利用后,命令以 nginx worker 进程权限执行。取得宿主机 root 权限需要串联另一项 Linux 内核漏洞。 https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities 利用条件:均无需登录,但必须满足对应版本和配置条件。 1、CVE-2026-123007(影响面最广):使用未修复的 nginx、构建中包含 HTTP/2 模块,且在攻击者可访问的监听端口启用了 HTTP/2。官方受影响版本为 1.9.5–1.31.8。仅凭版本号不能判断风险,还需核实实际构建、运行配置及发行版是否已回补修复。 2、CVE-2026-123634:配置 resolver,反向代理目标由请求变量决定,并存在 mirror 等子请求,还涉及 mirror_request_body off。 3、CVE-2026-123633:通过 HTTP/2 接收请求,并将请求转发至后端服务且 worker 连接数接近上限。 4、CVE-2026-121810:启用 HTTP/3,并将请求反向代理至后端服务。 5、CVE-2026-113425:启用 nginx 邮件代理,同时使用 proxy on 和 auth_http。 🛡️ 安全建议: 1、优先核查对外开放 HTTP/2 的 nginx 实例,并逐项比对其余漏洞的配置条件; 2、NGINX Open Source 1.31 分支升级至 1.31.9+,1.30 分支升级至 1.30.7+;使用 NGINX Plus 或发行版软件包的,应按对应厂商公告确认修复版本及回补情况; 3、无法立即升级时,可暂时关闭受影响端口的 HTTP/2,但这只能阻断其中两条路径。更新程序后还需重启 nginx 或完成受支持的二进制热升级,仅重新加载配置不能替换旧程序。

🚨 Nginx 史诗级漏洞预警:NGINX2Root 今天凌晨,Nginx 爆出潜伏 10 余年的高危漏洞链 NGINX2Root,共 5 个 CVE,CVSS 4.0 评分 9.2。 只要服务器对外开启了 HTTP/2,未经认证的攻击者就可能远程执行代码。配合 Linux 内核提权漏洞,还可进一步逃逸 Docker、拿下宿主机 root。 📌 核心漏洞 CVE-2026-123007(HTTP/2,最严重) CVE-2026-123633 / CVE-2026-123634 CVE-2026-121810 / CVE-2026-113425 📌 受影响版本 Nginx 1.9.5 ~ 1.31.8(HTTP/2 漏洞) 即自 2015 年引入 HTTP/2 以来的几乎所有版本 🔍 一秒自查 在终端运行: openssl s_client -connect 你的域名:443 -alpn h2 如果返回结果里出现 ALPN protocol: h2,说明已对外暴露 HTTP/2,在受影响范围内。 再顺手查一下 Nginx 的 error.log,如果近期出现莫名的 worker process exited on signal 异常退出记录,建议重点排查是否已被扫描试探。 🛠 修复方法 立即升级到修复版本,并重启 Nginx(只 reload 不够): 稳定版:1.30.7 主线版:1.31.9 暂时无法升级的,先关闭 HTTP/2 临时缓解: http2 off; 注意:关 HTTP/2 只能堵住两个 HTTP/2 漏洞,不能替代升级。 有线上服务的,今晚就升,别拖。 来源:http://nginx.org 安全公告 / Xint NGINX2Root 披露 #Nginx #漏洞预警 #服务器安全

On November 18, 2026, F5 and http://nginx.org disclosed ten NGINX vulnerabilities fixed in 1.31.9 and 1.30.7. Five of these vulnerabilities are grouped as "nginx2root" and can allow unauthenticated attackers to crash a worker process or execute code: • CVE-2026-123007 — HTTP/2 flow-control underflow • CVE-2026-123633 — HTTP/2 proxy use-after-free • CVE-2026-121810 — HTTP/3/QUIC use-after-free • CVE-2026-123634 — resolver use-after-free • CVE-2026-113425 — mail proxy use-after-free Please make a server snapshot backup before proceeding with the operation Upgrade: Open the App Store, click the "Update App List" button in the top right corner, find Nginx and update it to 1.31.9 or 1.30.7. Switch version: Upgrading from an older version to the latest version may cause configuration issues. After switching versions, please upgrade the version again. Open App Store → Nginx → Switch version. Temporary fix — disable HTTP/2. Back up first, then replace, verify and restart: BK=/www/backup/nginx_vhost_$(date +%F_%H%M); mkdir -p $BKcp -a /www/server/panel/vhost/nginx/. $BK/grep -rl "http2 on;" /www/server/panel/vhost/nginx/ | xargs -r sed -i 's/http2 on;/http2 off;/g' /www/server/nginx/sbin/nginx -t /etc/init.d/nginx restart

🚨 Nginx 史诗级漏洞预警:NGINX2Root 今天凌晨,Nginx 爆出潜伏 10 余年的高危漏洞链 NGINX2Root,共 5 个 CVE,CVSS 4.0 评分 9.2。 只要服务器对外开启了 HTTP/2,未经认证的攻击者就可能远程执行代码。配合 Linux 内核提权漏洞,还可进一步逃逸 Docker、拿下宿主机 root。 📌 核心漏洞 CVE-2026-123007(HTTP/2,最严重) CVE-2026-123633 / CVE-2026-123634 CVE-2026-121810 / CVE-2026-113425 📌 受影响版本 Nginx 1.9.5 ~ 1.31.8(HTTP/2 漏洞) 即自 2015 年引入 HTTP/2 以来的几乎所有版本 🔍 一秒自查 在终端运行: openssl s_client -connect 你的域名:443 -alpn h2 如果返回结果里出现 ALPN protocol: h2,说明已对外暴露 HTTP/2,在受影响范围内。 再顺手查一下 Nginx 的 error.log,如果近期出现莫名的 worker process exited on signal 异常退出记录,建议重点排查是否已被扫描试探。 🛠 修复方法 立即升级到修复版本,并重启 Nginx(只 reload 不够): 稳定版:1.30.7 主线版:1.31.9 暂时无法升级的,先关闭 HTTP/2 临时缓解: http2 off; 注意:关 HTTP/2 只能堵住两个 HTTP/2 漏洞,不能替代升级。 有线上服务的,今晚就升,别拖。 来源:http://nginx.org 安全公告 / Xint NGINX2Root 披露 #Nginx #漏洞预警 #服务器安全
15 of 15 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | f5 | dos | - | nginx | - |
| App | f5 | nginx_gateway_fabric | - | - | - |
| App | f5 | nginx_ingress_controller | - | - | - |
| App | f5 | nginx_ingress_controller | - | - | - |
| App | f5 | nginx_ingress_controller | 3.7.1 | - | - |
| App | f5 | nginx_ingress_controller | 3.7.2 | - | - |
| App | f5 | nginx_ingress_controller | 4.0.0 | - | - |
| App | f5 | nginx_ingress_controller | 4.0.1 | - | - |
| App | f5 | nginx_instance_manager | - | - | - |
| App | f5 | nginx_open_source | - | - | - |
| App | f5 | nginx_plus | - | - | - |
| App | f5 | nginx_plus | r34 | - | - |
| App | f5 | nginx_plus | r35 | - | - |
| App | f5 | nginx_plus | r36 | - | - |
| App | f5 | waf | - | nginx | - |