Skip to content
IT
Cybersecurity

Critical Vulnerabilities in NGINX: Immediate Patch for 225 Million Sites

CVE-2026-123633 and CVE-2026-123007: how to protect servers and applications

Published on By Sebastiano, GoYou.it 7 min read
Listen to the full article Full reading · 12:24 · from the channel GoYou Cybersecurity
Critical Vulnerabilities in NGINX: Immediate Patch for 225 Million Sites

KEY TAKEAWAYS

  • Two critical vulnerabilities in NGINX (CVE-2026-123633 and CVE-2026-123007) with CVSS 9.2
  • Affect NGINX OSS and Plus with HTTP/2 enabled, exposing to code execution
  • Immediate patches available for NGINX OSS 1.30.7 and NGINX Plus 37.0.7.1
  • Temporary solutions with Cloud WAF to mitigate the attack
  • Potential impact extended to more applications for reverse proxy configurations

Two Critical Vulnerabilities in NGINX Exposed to Potential Remote Execution Attacks

F5 has released security updates for two critical vulnerabilities in NGINX, the popular open-source web server and reverse proxy used by approximately 225 million websites. The flaws, discovered independently by five research teams, were reported to F5 as part of a coordinated disclosure. Both vulnerabilities, rated with a CVSS 4.0 score of 9.2, involve memory security defects in how NGINX handles HTTP/2 traffic.

Quick Response

  • The vulnerabilities CVE-2026-123633 and CVE-2026-123007 allow remote code execution on NGINX servers with HTTP/2 enabled
  • Affect NGINX OSS versions starting from 1.19.7 and specific NGINX Plus versions
  • Cloud WAF solutions offer temporary protection until the patch
  • The impact can extend to multiple applications and websites managed by the same server

Technical Details of the Vulnerabilities

The first vulnerability, identified as CVE-2026-123633, is a "use-after-free" in the HTTP/2 connection handler. It occurs when available connection slots are scarce during the reverse-proxy process. The second, CVE-2026-123007, is an "integer underflow" in the HTTP/2 flow-control mechanism (send_window). Both can be exploited by unauthenticated attackers to execute code on the server.

Potential Impact and Attack Scenarios

Experts have demonstrated code execution on NGINX servers serving static files, without the need for backend applications or third-party modules. This makes the vulnerabilities particularly dangerous as they target the core of NGINX itself. A successful attack could allow attackers to execute commands, steal sensitive data, manipulate websites, or disrupt services. Given NGINX's role as a reverse proxy, a single compromised server could compromise multiple applications and services.

Scope of Affected Versions

CVE-2026-123633 affects NGINX OSS starting from version 1.19.7, while CVE-2026-123007 traces back to even older versions, dating back to NGINX 1.9.5, released in 2015. This wide scope of affected versions makes the situation particularly critical for many organizations that may have neglected regular updates.

Temporary Solutions and Mitigation Measures

Imperva has reported that its Cloud WAF and WAF gateway solutions offer immediate protection against both vulnerabilities. As an additional measure, users can choose the HTTP/2 "client to Imperva" option only, which disables HTTP/2 between Imperva and the origin server, thus protecting the vulnerable server while the patch is applied. This configuration maintains the performance benefits of HTTP/2 for end users.

Patches and Updates Available

F5 has released patches for both vulnerabilities. For NGINX OSS, the corrected versions are 1.30.7 (stable) and 1.31.9 (mainline). For NGINX Plus, the patches are specific to each vulnerability: CVE-2026-123633 is resolved in versions 37.0.7.1 and 37.2.0.1, while CVE-2026-123007 requires versions 37.0.8.1 and 37.3.0.1. Administrators are advised to update as soon as possible.

Implications for Cyber Insurance and Compliance

The discovery of these critical vulnerabilities underscores the importance of adequate cyber insurance and a well-structured incident response. Affected organizations may face significant costs for breach remediation, making adequate insurance coverage crucial. Additionally, the need for immediate patches highlights the importance of a managed Security Operations Center or an MDR service to monitor and promptly respond to such threats.

Considerations for NIS2 and DORA Compliance

These vulnerabilities represent a case study for the importance of NIS2 compliance and digital operational resilience in accordance with the DORA regulation. Organizations must ensure that their systems are up-to-date and have clear procedures for managing vulnerabilities. The discovery of flaws in fundamental components like NGINX demonstrates how even seemingly stable systems can hide significant risks.

Analysis of Causes and Technical Implications

The vulnerabilities stem from fundamental defects in memory management and integer calculations in HTTP/2 protocols. This underscores the importance of rigorous testing and adequate Data Loss Prevention, as even seemingly secure components can become attack vectors. The extensive nature of the affected versions highlights the need for a proactive approach to security, with regular penetration tests and vulnerability assessments.

Future Perspectives and Recommendations

At this point, while patches are available, it is essential that organizations apply them immediately. The discovery of these vulnerabilities should serve as a reminder of the importance of ISO 27001 certification and regular security audits. Additionally, considering the potential impact, organizations should evaluate the implementation of a SIEM for better visibility of security events and robust ransomware protection to prevent secondary attacks.

Improvements in Vulnerability Management

This incident highlights the importance of disaster recovery as a service (DRaaS) and reliable enterprise backup. Organizations should also consider implementing a zero trust architecture to limit the impact of any future vulnerabilities. Furthermore, with the increase in targeted attacks, robust identity access management (IAM) becomes crucial to prevent unauthorized access.

Market Overview: NGINX and the Web Ecosystem

NGINX holds a 39% market share among web servers, according to W3Techs statistics. This makes it the second most widely used server after Apache. Its popularity is due to its efficiency in handling a high number of simultaneous connections, making it particularly attractive for high-traffic sites. However, this widespread use amplifies the impact of the discovered vulnerabilities, as each unpatched installation represents a potential entry point for attacks.

Emerging Trends in HTTP/2 Security

The vulnerabilities CVE-2026-123633 and CVE-2026-123007 highlight a concerning trend in the security of modern protocols. HTTP/2, introduced to improve web performance, is becoming an increasingly frequent target for attackers. According to a Menlo Security report, 42% of web server vulnerabilities detected in 2026 are related to next-generation protocols like HTTP/2 and QUIC.

Impact on Organizations: Costs and Complexity

Companies using NGINX face significant costs for mitigation and patching. According to a Gartner analysis, the average cost for managing a single critical vulnerability in an enterprise web server exceeds €120,000, considering both internal and external resources needed for updating and testing. This includes downtime for applying patches and regression testing to ensure system stability.

Implications for Risk Management

The NGINX vulnerabilities underscore the importance of accurate risk assessment. Organizations must consider not only the likelihood of an attack but also the potential impact on critical assets. This requires a structured approach to risk management, including dependency analysis, impact assessment, and the implementation of appropriate mitigation measures.

Advanced Mitigation Strategies

In addition to immediate patches, organizations can adopt advanced mitigation strategies. For example, implementing a web application firewall (WAF) can provide additional protection against HTTP/2-based attacks. Furthermore, using an intrusion detection and prevention system (IDS/IPS) can help identify and block attempts to exploit the vulnerabilities.

Best Practices for Updating NGINX

To ensure a secure and effective update, organizations should follow best practices for managing updates. This includes testing patches in a staging environment before implementing them in production, documenting changes, and planning a rollback in case of issues. Additionally, it is essential to maintain an up-to-date inventory of systems to quickly identify vulnerable installations.

Future Trends in Web Server Security

The NGINX vulnerabilities reflect a broader trend towards increasing complexity in web server security. With the adoption of more advanced protocols and the rise of threats, organizations must take a proactive approach to security. This includes investing in advanced security technologies, continuous staff training, and collaborating with vendors for the timely release of patches.

A Turning Point for Web Security

The vulnerabilities in NGINX represent a turning point for web security. They highlight the need for a more robust approach to vulnerability management, including not only immediate patching but also advanced mitigation strategies and accurate risk assessment. For organizations, this means investing in advanced security technologies and adopting best practices for managing updates. Only in this way will it be possible to face the future challenges of web security.

Frequently Asked Questions

What is the impact of these vulnerabilities on NGINX?

The vulnerabilities can allow attackers to execute remote code on NGINX servers with HTTP/2 enabled, potentially compromising multiple applications and services managed by the same server.

How can I protect my NGINX server?

You can use Cloud WAF solutions as a temporary measure and immediately apply the available patches for NGINX OSS and NGINX Plus.

Which versions of NGINX are affected?

What are the available solutions to mitigate these vulnerabilities?

Imperva offers immediate protection through its Cloud WAF and WAF gateway solutions. Additionally, you can configure HTTP/2 only between the client and Imperva to protect the origin server.

What are the implications for NIS2 and DORA compliance?

These vulnerabilities underscore the importance of NIS2 compliance and digital operational resilience in accordance with the DORA regulation, requiring clear procedures for managing vulnerabilities.

Editorial Note and Disclaimer

The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.

GoYou does not constitute a journalistic publication nor an editorial product pursuant to Law No. 62/2001 and does not provide real-time information.

The GoYou project does not provide professional, technical, legal, or financial advice and disclaims any liability for the misuse of the information published.

In the Crypto sector, every investment involves risks: readers are invited to always inform themselves autonomously before making any decision.

Source: imperva.com · GoYou.it is not a registered news outlet; all content is for informational and educational purposes.

Listen GoYou Cybersecurityevery article read in full
Go to the channel

You may also like

Behind every article is the work of our passion. If you enjoy GoYou.it, you can support its development and continuity.

Support with PayPal