NEWS / LATEST UPDATES
Our Response to the NGINX HTTP/2 Vulnerabilities (CVE-2026-123007 / CVE-2026-123633)
On November 18, 2026, F5 disclosed critical vulnerabilities (CVE-2026-123007 / CVE-2026-123633) in the HTTP/2 implementation of the NGINX web server. According to the reports, these vulnerabilities could allow an unauthenticated remote attacker to execute arbitrary code on NGINX servers with HTTP/2 enabled (CVSS v4.0 base score: 9.2).
We began investigating immediately and have put in place the measures that are currently available. Our response is described below.
About the Vulnerabilities
- CVE-2026-123007: A flaw in HTTP/2 flow control that can cause a heap buffer overflow.
- CVE-2026-123633: A flaw in HTTP/2 connection handling that can cause a use-after-free. It is reported to be more likely to be exploited when NGINX is used as a reverse proxy.
Both affect configurations with HTTP/2 enabled. Fixed versions are available as NGINX 1.30.7 (stable) and 1.31.9 (mainline).
Affected Systems
Web servers and web systems developed or maintained by us that use NGINX with HTTP/2 enabled.
Our Response
On environments where a fixed version is not yet available as an OS package, we have disabled HTTP/2 as a workaround. Connections continue over HTTP/1.1, so there is no impact on viewing or using the affected websites and web systems.
Next Steps
As soon as fixed packages become available for each environment, we will apply them in turn after verifying that everything works correctly. We plan to re-enable HTTP/2 once the fixes have been applied.
There is nothing customers need to do regarding this matter at this time. If you have any questions or concerns about a specific system, please contact your representative or reach out to us through our contact form.
This notice reflects the information available at the time of publication. We will update this page as the situation develops.