What happened
On November 18, 2026, security researchers disclosed five critical vulnerabilities in nginx that can allow unauthenticated remote code execution: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. The two most severe affect HTTP/2 handling. The researchers also showed that chaining them with a Linux kernel flaw can give an attacker root access to the host, even from inside a container.
No public exploit and no attacks have been reported so far. F5 has released fixed versions nginx 1.30.7 (stable) and 1.31.9 (mainline). See the F5 advisory.
Exploitation: We have found no indication of exploitation of Dynatrace systems.
What this means for Dynatrace
| Component | Status | Why |
|---|---|---|
| Dynatrace Managed | Not affected | Managed ships its own nginx build without the HTTP/2 module. To verify, run <installation directory>/nginx/sbin/nginx -V on a cluster node (default: /opt/dynatrace-managed/nginx/sbin/nginx -V). The output does not contain --with-http_v2_module. |
| OneAgent | Not affected | OneAgent does not include nginx. When monitoring nginx, it runs inside the monitored nginx installation, which determines exposure. |
| ActiveGate | Not affected | ActiveGate does not include or use nginx. |
| Synthetic | Not affected | Synthetic does not include or use nginx. |
| Dynatrace SaaS and other Dynatrace-operated services | Mitigation and patching in progress | A limited number of edge and supporting services use nginx. Where HTTP/2 was enabled, we disabled it, which blocks the two most severe vulnerabilities. We are upgrading all affected services to fixed nginx versions. |
Update: OneAgent support for patched nginx versions is now available
OneAgent now supports the fixed nginx versions 1.30.7 and 1.31.9. To monitor a patched nginx, update OneAgent to one of the versions below. Until you update, OneAgent will not monitor a patched nginx. The patched nginx itself keeps working normally.
| OneAgent release | Version with nginx 1.30.7 and 1.31.9 support |
|---|---|
| 1.349 | 1.349.123.20261119-125418 |
| 1.347 | 1.347.81.20261119-151213 |
| 1.345 | 1.345.100.20261119-152018 |
| 1.343 | 1.343.128.20261119-111155 |
| 1.341 | 1.341.100.20261119-121523 |
| 1.339 | 1.339.100.20261119-162702 |
What you should do
Upgrade nginx to 1.30.7 or 1.31.9, or to your Linux distribution’s patched package. Don’t rely on the version string alone: distributions such as Ubuntu backport fixes without changing it, so check your vendor’s advisory.
Until you can patch, reduce exposure:
- Disable HTTP/2 (
http2 off, or removehttp2fromlistendirectives), then reload nginx and confirm old worker processes have exited. - Disable HTTP/3 and QUIC if not needed.
- Replace
proxy_passtargets that use variables with fixed upstreams. - Restrict access to the nginx mail proxy, if used.
- Apply current Linux kernel updates to block the privilege escalation step.
Check Kubernetes ingress controllers. The community ingress-nginx controller enables HTTP/2 by default and is no longer maintained. Set use-http2: "false" in its ConfigMap and plan a migration to a maintained ingress.
Note on CDNs and WAFs. A CDN or WAF that terminates HTTP/2 in front of nginx may reduce the risk, depending on the implementation. Do not treat this as a fix.
Find nginx in your environment with Dynatrace. This query lists monitored nginx instances by version:
fetch dt.entity.process_group_instance, from:now()-2h
| expand t = softwareTechnologies
| filter startsWith(t, "type:NGINX")
| parse t, "LD 'version:' (LD '/')? LD:version EOS"
| fieldsAdd ingress_controller = contains(lower(entity.name), "ingress")
| summarize instances = count(), by:{version, ingress_controller}
| sort instances desc
Update history
| Date | Update |
|---|---|
| November 20, 2026 | Added OneAgent versions with support for patched nginx 1.30.7 and 1.31.9. |
| November 19, 2026 | Added a component status overview, the Managed verification command, the OneAgent compatibility note and guidance. |
| November 19, 2026 | Confirmed that Managed, OneAgent, ActiveGate and Synthetic are not affected. Investigation of edge components continued, with patches applied where necessary. No indication of active exploitation of Dynatrace systems. |
| November 18, 2026 | First publication |