Tree News

GoPlus Security 🚦 · 2026-11-19 03:23 UTC

🚨 GoPlus Security Alert: Five nginx2root Vulnerabilities Disclosed—Check HTTP/2-Enabled Deployments First On November 18, NGINX released security updates addressing five nginx2root vulnerabilities, including CVE-2026-123007. These are independent attack paths affecting different configurations. Successful exploitation allows arbitrary code execution with the privileges of an nginx worker process. The demonstrated attack chain achieves root access on the host by chaining a separate Linux kernel privilege escalation vulnerability. 📌 Exploitation Conditions All five vulnerabilities can be exploited without authentication when their respective version and configuration requirements are met. 1. CVE-2026-123007 (broadest exposure): An unpatched nginx build includes the HTTP/2 module, with HTTP/2 enabled on a listener reachable by the attacker. The officially affected versions are 1.9.5–1.31.8. Version numbers alone do not establish exposure—check the actual build, active configuration, and whether the distribution has backported a fix. 2. CVE-2026-123634: A resolver is configured, the proxy_pass destination is derived from request data, and mirror is used with mirror_request_body off. 3. CVE-2026-123633: nginx receives requests over HTTP/2 and proxies them to an upstream server while available connection slots in the worker are running low. 4. CVE-2026-121810: HTTP/3 is enabled, and requests are reverse-proxied to an upstream server. 5. CVE-2026-113425: The nginx mail proxy is enabled with both proxy on and auth_http configured. 🛡️ Security Recommendations 1. Prioritize internet-facing nginx instances with HTTP/2 enabled, then check the configuration requirements for the remaining vulnerabilities. 2. Upgrade NGINX Open Source 1.31 deployments to 1.31.9 or later, and 1.30 deployments to 1.30.7 or later. For NGINX Plus or distribution packages, consult the relevant vendor advisories to confirm patched releases and backported fixes. 3. If you cannot upgrade immediately, temporarily disable HTTP/2 on affected listeners. Apply the configuration change and confirm that the old worker processes have exited. This mitigates only the two HTTP/2 attack paths. After installing the patched binary, restart nginx or perform a supported live binary upgrade. Reloading the configuration alone does not replace the running binary.

Loading the story on Tree News…