PHP警告所有受支持版本存在严重安全漏洞,修复将于11月19日发布 · 4h 10年旧的NGINX HTTP/2漏洞允许未经身份验证的攻击者在服务器上执行代码 · 14h F5 警告 6 个关键 BIG-IP 漏洞可能导致特定设置下的流量崩溃,并可能允许远程代码执行 · 15h CVE-2026-123633 和 CVE-2026-123007:关键的 NGINX HTTP/2 漏洞 · 16h Apache Roller 中的关键 RCE 漏洞正在被积极利用,无需身份验证 · 16h Java4Shell 漏洞威胁全球企业及 Java 应用生态系统 · 16h Cloudflare WAF 如何帮助防御 Java4Shell (CVE-2026-114938) · 18h LMS软件中的漏洞 · 20h 新攻击绕过TPM锁定,在几天内破解Windows Hello和BitLocker PIN,而不是几年 · 21h 针对Web应用的AI渗透测试检查清单:选择供应商前要问的15个问题 · 21h PHP警告所有受支持版本存在严重安全漏洞,修复将于11月19日发布 · 4h 10年旧的NGINX HTTP/2漏洞允许未经身份验证的攻击者在服务器上执行代码 · 14h F5 警告 6 个关键 BIG-IP 漏洞可能导致特定设置下的流量崩溃,并可能允许远程代码执行 · 15h CVE-2026-123633 和 CVE-2026-123007:关键的 NGINX HTTP/2 漏洞 · 16h Apache Roller 中的关键 RCE 漏洞正在被积极利用,无需身份验证 · 16h Java4Shell 漏洞威胁全球企业及 Java 应用生态系统 · 16h Cloudflare WAF 如何帮助防御 Java4Shell (CVE-2026-114938) · 18h LMS软件中的漏洞 · 20h 新攻击绕过TPM锁定,在几天内破解Windows Hello和BitLocker PIN,而不是几年 · 21h 针对Web应用的AI渗透测试检查清单:选择供应商前要问的15个问题 · 21h
🛡️
ACyber Sentinel 安全评估团队
← 返回
⚡ 情报报告

10年旧的NGINX HTTP/2漏洞允许未经身份验证的攻击者在服务器上执行代码

NGINX的HTTP/2支持中的一个漏洞允许攻击者在启用HTTP/2的服务器上运行代码,而无需登录。

这个存在了十年的漏洞,CVE-2026-123007,被称为“nginx2root”,自2015年9月22日发布的1.9.5版本以来就存在于NGINX的开源代码中。修复版本1.31.9和1.30.7今天发布。

F5公司表示,攻击者可以在ASLR关闭或可以被绕过的情况下运行代码。Wiz的安全研究人员表示,他们在测试中绕过了ASLR并通过该漏洞运行了代码。Xint的研究人员表示,他们仅通过可访问的HTTP/2端口就运行了代码。

以这种方式运行的代码获得了NGINX工作进程的权限。根据卢森堡计算机事件响应中心(CIRCL)的说法,获取主机的root权限需要另一种提升权限的方法。

在Xint的测试中,作为工作进程运行的代码可以通过Linux内核SCTP代码中的一个独立漏洞获得主机的root权限,即使NGINX在Docker容器内运行。

截至目前,供应商、Wiz和Rapid7的研究人员尚未报告任何利用该漏洞的攻击。CISA的已知利用漏洞目录截至今天未列出该漏洞。

该漏洞的概念验证代码已在GitHub上公开,但其说明指出仅适用于演示针对同一机器上新启动的Docker容器的攻击。

根据NGINX的安全公告,从1.9.5到1.31.8的每个开源版本都是易受攻击的。这包括10月21日的1.31.8版本,以及10月14日的安全发布版本1.31.7和1.30.6。

Wiz PoC

NGINX Plus也受到影响,在修复构建之前的37.x版本和R34到R36版本中,供应商公告指出。

今天的发布还修复了四个其他漏洞,供应商表示这些漏洞可能在相同的ASLR条件下导致代码执行。它们在CVSS 4.0中均得分9.2(满分10分)。

每个漏洞只能在特定设置中被触发:

漏洞

所需条件

CVE-2026-123007

开启HTTP/2

CVE-2026-123633

HTTP/2,工作进程在worker_connections不足的情况下将请求传递给后端服务器

CVE-2026-123634

由变量构建的代理服务器名称,加上服务器端包含(SSI)或镜像子请求到查找相同名称的位置

CVE-2026-121810

开启HTTP/3

CVE-2026-113425

NGINX用作邮件代理

HTTP/2在包含http2的listen指令中开启,或设置http2开启。使用-openssl s_client -alpn h2对服务器进行测试可以显示其是否接受HTTP/2:如果接受,输出为ALPN protocol: h2。在CDN后面,测试NGINX源本身,因为仅接受HTTP/1.1的源无法通过HTTP/2进行攻击。

修复、解决方法和攻击迹象

根据F5的说法,这些发布修复了CVE-2026-123007:

NGINX Open Source 1.31.0到1.31.8(主线):在1.31.9中修复

NGINX Open Source 1.9.5到1.30.6,包括较旧的分支如1.28:在1.30.7中修复

NGINX Plus 37.1.0到37.2.0.1:在37.3.0.1中修复

NGINX Plus 37.0.0到37.0.7.1:在37.0.8.1中修复

NGINX Plus R34到R36:未列出修复

根据NGINX的发布说明,版本1.31.9和1.30.7修复了所有五个漏洞。在NGINX Plus中,37.3.0.1和37.0.8.1修复了四个漏洞,CVE-2026-123633的修复在早期构建37.2.0.1和37.0.7.1中引入。

升级后,完全重启NGINX或使用其实时二进制升级。仅重新加载会使旧可执行文件继续运行,现有连接可能会保持在旧工作进程上。

截至今天,NGINX的官方Docker镜像已标记为1.31.9和1.30.7,包括Alpine变体。

截至今天,Ubuntu和Debian尚未发布修复包。Ubuntu的CVE状态页面列出了16.04到26.10版本的nginx为易受攻击,Debian的安全跟踪器在bookworm、trixie、forky和sid中列出了它为易受攻击。一个发行版包可以在不更改nginx -v报告的版本号的情况下携带修复,因此请比较完整的包版本与发行版自己的公告。

Xint PoC

供应商仅列出了五个漏洞中两个的解决方法。对于解析器漏洞CVE-2026-123634,避免使用SSI和镜像指令,并且不要从变量构建代理服务器名称。对于邮件代理漏洞CVE-2026-113425,将监听器限制在受信网络。

CIRCL的响应指导建议在您能够升级之前暂时关闭HTTP/2。这可以阻止CVE-2026-123007和CVE-2026-123633,但无法阻止其他三个漏洞。在使用HTTP/3的地方关闭它可以消除CVE-2026-121810所需的设置。

在NGINX 1.25.1及更高版本中,在每个受影响的服务器块中设置http2 off;并从其listen指令中删除http2。在1.9.5到1.25.0中,从listen指令中删除http2,因此listen 443 ssl http2;变为listen 443 ssl;。然后在需要的地方重启NGINX,并重新运行openssl检查以确认服务器不再接受HTTP/2。

在Linux内核的SCTP漏洞修复之前,同样的指导建议不使用SCTP的主机阻止其内核模块加载。一个方法是在/etc/modprobe.d/中的.conf文件中添加行install sctp /bin/false。这不会卸载已经加载的模块或关闭内置于内核中的SCTP。

对于攻击迹象,CIRCL建议查找启动意外程序的NGINX工作进程、异常退出或留下核心转储的工作进程、具有大量传入流量但记录请求较少的长期HTTP/2连接,以及异常的外部连接或DNS查找。干净的访问日志并不能排除攻击,因为HTTP/2控制帧通常不会作为请求出现在那里。以上任何迹象单独都不是证据。

根据Rapid7的技术分析,攻击需要大约128 GB的HTTP/2流量。攻击在其演示中持续了两分半钟。在低于约300 Mbit/s的链接上,传输将超过NGINX的默认一小时连接限制,攻击将失败。

该方法还依赖于glibc me

相关漏洞

CVE-2026-123634 CVSS 9.2 CRITICAL Received
CVE-2026-123634 - NGINX resolver vulnerability
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.
CVE-2026-123633 CVSS 9.2 CRITICAL Received
CVE-2026-123633 - NGINX ngx_http_v2_module vulnerability
When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or may allow a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-123007 CVSS 9.2 CRITICAL Received
CVE-2026-123007 - NGINX ngx_http_v2_module vulnerability
This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-121810 CVSS 9.2 CRITICAL Received
CVE-2026-121810 - NGINX ngx_http_v3_module vulnerability
Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, unauthenticated attacker can cause a use-after-free condition in the NGINX worker process, leading to a restart. Exploitation also depends on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-113425 CVSS 9.2 CRITICAL Received
CVE-2026-113425 - NGINX ngx_mail_proxy_module vulnerability
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-118383 CVSS 10 CRITICAL Analyzed
CVE-2026-118383 - Pre-authentication use-after-free in MongoDB Server replica set primary catch-up
A use-after-free in the replication component of MongoDB Server can occur when a newly elected replica set primary completes catch-up. The condition can be caused by requests that do not require authentication, and may result in the server terminating unexpectedly or, under certain conditions, arbitrary code execution in the context of the server process. Replica set members are affected, including the shard and config server replica set members of sharded clusters; standalone mongod instances are not.