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

F5 在十月安全更新中解决多个 NGINX 漏洞

F5 和 NGINX 项目于 2026 年 10 月 14 日发布了安全修复,解决了 NGINX Open Source 和 NGINX Plus 中的五个漏洞。这些问题影响内存处理、HTTP/3 请求处理和 TLS 会话安全。F5 为其中三个漏洞分配了 CVSS 4.0 评分 9.2,突显了在特定条件下的潜在影响。NGINX 被广泛用作 Web 服务器、反向代理、负载均衡器和应用流量网关。这些组件中的漏洞不仅会影响网站可用性:根据配置和缺陷,它还可能使应用程序暴露于请求操控或工作进程的妥协。重要的区别在于,这些漏洞并不以相同的方式影响每个安装。有些需要特定的 NGINX 指令或功能被启用。因此,管理员在决定响应之前应评估已安装的版本和活动配置。

五个需要了解的漏洞

10 月 14 日发布修复了 NGINX Open Source 中的五个漏洞。

1. CVE-2026-15176 — 涉及别名和重写的缓冲区溢出

此漏洞发生在配置了别名指令并同时使用重写和引用 $request_filename 的 set 或 return 指令的位置。当在访问日志格式中使用该变量时,也可能出现类似情况。经过精心构造的 HTTP 请求可以触发 NGINX 工作进程中的堆缓冲区溢出,可能导致拒绝服务条件。当地址空间布局随机化(ASLR)被禁用或可以被绕过时,代码执行也可能成为可能。F5 将此漏洞评为 CVSS 4.0:9.2(严重)。

2. CVE-2026-93479 — 脚本评估中的缓冲区溢出

此漏洞影响 NGINX 在评估涉及变量的字符串表达式时,特别是在使用 map 指令进行正则表达式匹配的配置下。在相关条件下,攻击者可以触发工作进程中的缓冲区溢出。潜在后果包括服务中断,并且在特定情况下可能导致代码执行。F5 将此漏洞分配 CVSS 4.0 评分 9.2(严重)。

3. CVE-2026-97205 — 涉及异步文件 I/O 的使用后释放

此问题影响启用了异步文件 I/O(AIO)的配置,并且服务器端包含(SSI)页面使用了 include 虚拟命令。当特殊构造的请求触发易受攻击的代码路径时,使用后释放条件可能会损坏工作进程内存。这可能导致工作进程崩溃,或者在特定条件下导致代码执行。F5 将此漏洞分配 CVSS 4.0 评分 9.2(严重)。配置要求很重要:不使用受影响组合的部署可能不会暴露于此特定攻击路径。

4. CVE-2026-95101 — HTTP/3 请求体注入

此漏洞影响 ngx_http_v3_module,当启用 HTTP/3 且 proxy_request_buffering 指令开启时。未经身份验证的攻击者可能能够向代理请求注入数据。根据应用程序如何处理请求,这可能会影响请求的完整性以及转发到上游服务的流量处理。报告的影响是请求注入,而不是与前三个漏洞相关的内存损坏行为。

5. CVE-2026-97629 — TLS 会话伪造

此漏洞涉及 TLS 会话票证和密钥轮换。会话票证处理中的弱点可能允许在安全通告中描述的条件下进行会话伪造。由于 TLS 会话管理是客户端与服务之间安全边界的一部分,管理员应将此问题与内存安全和 HTTP/3 缺陷一起评估,而不是仅专注于最高的 CVSS 评分。

受影响和修复版本

对于 NGINX Open Source,10 月 14 日发布提供了以下版本中所有五个漏洞的修复。

NGINX Open Source

稳定分支:升级到该分支的 1.30.6 或更高版本。

主线分支:升级到该分支的 1.31.7 或更高版本。

NGINX Plus

版本 37.0:F5 列出 37.0.5.1 作为修复三个关键内存安全漏洞的版本。

版本 37.1:F5 列出 37.1.0.1 作为修复这三个漏洞的版本。

重要提示:这些 NGINX Plus 版本不应自动假定解决每个分支中通告中的所有问题。在升级之前,请确认与各个 F5 通告的确切版本和修复状态。

其他 F5 产品需检查

安全通知还要求管理员评估其他包含 NGINX 组件的产品。根据产品和特定漏洞,这包括:

NGINX Ingress Controller

NGINX Gateway Fabric

NGINX Instance Manager

F5 WAF for NGINX

F5 DoS for NGINX

例如,F5 列出 NGINX Gateway Fabric 版本在 2.8.0 之前和 NGINX Instance Manager 版本在 2.24.0 之前受到此更新中至少一个漏洞的影响。NGINX Ingress Controller 和安全产品有其特定版本要求。请勿将 NGINX Open Source 版本号直接应用于这些产品。请检查其各自的 F5 产品通告和支持的升级路径。

安全团队现在应做什么

首先,列出外部暴露的 NGINX 实例、反向代理、入口控制器和应用网关。包括自我管理的安装和通过供应商包或容器镜像提供的产品。

接下来,验证确切版本并审查相关配置。特别注意别名、重写、映射、AIO、SSI、HTTP/3 和 TLS 会话票证设置。这些检查有助于识别在您的环境中可能可达的漏洞。

优先考虑三个内存安全漏洞,因为它们可能导致工作进程崩溃和条件代码执行。然而,不要因为 HTTP/3 请求注入和 TLS 会话伪造问题而不予以处理。

相关漏洞

CVE-2026-102764 CVSS 9.8 CRITICAL Analyzed
CVE-2026-102764 - BeyondTrust Remote Support Authentication Bypass by Spoofing Vulnerability - [Actively Exploited]
The vulnerability exists within internal components of BeyondTrust’s Remote Support product. The components did not adequately validate the origin of the messages it received. Under the right conditions, this could allow an attacker to perform file operations on the appliance.
CVE-2026-97629 CVSS 8.3 HIGH Awaiting Analysis
CVE-2026-97629 - NGINX ngx_http_ssl_module vulnerability
Description When NGINX Plus or NGINX Open Source is configured with ssl_session_cache shared:name:size without an explicit ssl_session_ticket_key file directives to automatically rotate SSL session ticket keys, a remote unauthenticated attacker is able to forge client SSL sessions in a non-deterministic manner that is beyond the attacker's control. An attacker could leverage this vulnerability to bypass verification of client certificates. Impact This vulnerability can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with access to sensitive information. 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-97205 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-97205 - NGINX ngx_http_core_module vulnerability
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_core_module module. When asynchronous file I/O (AIO) is enabled in certain configurations, processing a Server Side Includes (SSI) page containing “include virtual” commands may trigger a Use-After-Free (UAF) in the NGINX worker process. This may cause memory corruption or a worker process crash. 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, corrupt its memory, or possibly trigger 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-95101 CVSS 6.9 MEDIUM Awaiting Analysis
CVE-2026-95101 - NGINX ngx_http_v3_module vulnerability
Description NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_v3_module module. When using HTTP/3 with proxy_request_buffering on directive, an unauthenticated attacker may be able to inject data in the proxied request. Impact This vulnerability may allow remote attackers to inject data in the proxied request.  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-93479 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-93479 - NGINX map directive and regex matching vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. 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-15176 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-15176 - NGINX ngx_http_core_module vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a location is configured that uses the alias directive together with rewrite and a set or return directive referencing the $request_filename variable. Alternatively, the same result could be achieved when the $request_filename variable is used in an access log format directive. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. 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.