Executive summary
Optimizely is actively addressing five critical vulnerabilities disclosed in the NGINX web server, publicly known as “nginx2root.” As soon as they were disclosed, Optimizely Engineering and Security teams began reviewing our products and internal infrastructure.
No customer action is required for Optimizely-managed services at this time.
There is no evidence of exploitation across any Optimizely product or customer environment.
What happened
On November 18, 2026, F5 disclosed five memory-corruption vulnerabilities in NGINX Open Source and NGINX Plus. Researchers at Xint named the set “nginx2root.” All five are rated critical (CVSS 9.2), and an attacker doesn’t need to sign in to exploit them.
The most serious, CVE-2026-123007, is a flaw in nginx’s HTTP/2 handling that has been present since HTTP/2 support was added in 2015. Public proof-of-concept code exists for it. Depending on the setup, an attack could crash an nginx worker process or, potentially, run code.
| Vulnerability | Affects configurations with |
| CVE-2026-123007 | HTTP/2 enabled |
| CVE-2026-123633 | HTTP/2 enabled, with requests passed to a backend server |
| CVE-2026-123634 | A proxied server name built from variables, plus a server-side include or mirror subrequest |
| CVE-2026-121810 | HTTP/3 (QUIC) enabled |
| CVE-2026-113425 | nginx used as a mail proxy |
What we’re doing
Optimizely Engineering began reviewing all product lines and supporting infrastructure on November 18, 2026.
- We’ve assessed our products against all five vulnerabilities.
- Where nginx is in use and could be reached, we’ve disabled HTTP/2, stopped unused instances, or confirmed the vulnerable features aren’t enabled.
- All mitigations and available patches have been applied as of November 20.
Protections in place and customer actions
In many of our services, HTTP/2 traffic ends at a load balancer or edge service that then talks to nginx over HTTP/1.1. That keeps the most serious vulnerabilities out of reach, but we’ve still treated this as a critical issue and patched.
For Optimizely-managed solutions, updates are applied by Optimizely with no customer intervention needed.
If you run your own nginx
This applies if you host nginx yourself, for example in front of self-hosted Optimizely software:
- Upgrade to NGINX Open Source 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, check F5’s advisory for the fixed builds.
- Fully restart nginx after you upgrade. A reload doesn’t load the new binary.
- If you can’t upgrade today, disable HTTP/2 on internet-facing listeners. This reduces exposure to CVE-2026-123007 and CVE-2026-123633 only, and it isn’t a fix. Test first, because services that need HTTP/2, such as gRPC, will stop working.
- Operating system packages may be patched without changing the version number. Check your vendor’s advisory rather than relying on the version shown.
Evidence of exploit
Optimizely Security and Engineering teams have monitored our environments throughout this investigation and have found no evidence of exploitation related to these vulnerabilities across any Optimizely product or service.
How to contact us
If you have questions about this advisory, reach out to your Customer Success Manager (CSM) or contact Optimizely Support at support@optimizely.com.
Article is closed for comments.