{
    "file_item": {
        "filepath": "security-advisories",
        "filename": "CERT-EU-SA2026-022.pdf"
    },
    "title": "Critical vulnerabilities in Nginx",
    "serial_number": "2026-022",
    "publish_date": "18-11-2026 17:30:42",
    "description": "On 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process. <br>\nWhile researchers managed to successfully demonstrate the use of CVE-2026-123007, no exploitation in the wild has been reported yet.<br>\nIt is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances.  <br>\n",
    "url_title": "2026-022",
    "content_markdown": "---    \ntitle: 'Critical vulnerabilities in Nginx'\nnumber: '2026-022'\nversion: '1.0'\noriginal_date: '2026-11-18'\ndate: '2026-11-18'\n---\n\n_History:_\n\n* _18/11/2026 --- v1.0 -- Initial publication_\n\n\n# Summary\n\nOn 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process [1, 2]. \n\nWhile researchers managed to successfully demonstrate the use of CVE-2026-123007 [1], no exploitation in the wild has been reported yet.\n\nIt is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances.  \n\n# Technical Details\n\nThe vulnerability **CVE-2026-123007**, with a CVSS score of 8.1, is an integer overflow in HTTP/2 flow control which causes an out-of-bounds write on the heap. The only precondition is HTTP/2 enabled on a listening port.\n\nThe vulnerability **CVE-2026-123633**, with a CVSS score of 8.1, is a use-after-free flaw occurring when connection draining closes an active HTTP/2 connection while NGINX connects to an upstream server. HTTP/2 should be enabled and requests should be forwarded to an upstream server.\n\nThe vulnerability **CVE-2026-121810**, with a CVSS score of 8.1, is a use-after-free flaw occurring when a QUIC connection is drained during stream creation and upstream connection. HTTP/3 should be enabled and requests should be forwarded to an upstream server.\n\nThe vulnerability **CVE-2026-123634**, with a CVSS score of 8.1, is a use-after-free flaw occurring in the processing of the DNS resolver waiting list. a `resolver` must be set, a `proxy_pass` destination built from request data, and `mirror` with `mirror_request_body off` should be configured.\n\nThe vulnerability **CVE-2026-113425**, with a CVSS score of 8.1, is a use-after-free occurring when the client closes the connection during the `auth_http` authentication lookup. A mail proxy must be configured with `proxy on` and `auth_http`.\n\nAll five vulnerabilities can lead to unauthenticated code execution with the privileges of the NGINX worker process [1]. \n\n# Affected Products\n\nThe following products and versions are affected by one or more of the above vulnerabilities:\n\n- NGINX Open Source (mainline) from version 1.9.5 to 1.31.8 (range depends on the vulnerability, see Technical Details) [1]. Refer to the vendor advisory for the information on fixed versions [2].\n- NGINX Open Source (stable) versions 1.30.x, including the current stable version 1.30.6 [1, 3]. Refer to the vendor advisory for the information on fixed versions [2].\n- NGINX Plus from version 37.0.0 to 37.0.7.1, and 37.1.0 to 37.2.0.1. The versions R34, R35 and R36 are also affected [2]. Refer to the vendor advisory for the information on fixed versions [2].\n\n# Recommendations\n\nCERT-EU recommends updating vulnerable instance as soon as possible, prioritising internet-facing devices.\n\n## Compromise assessment\n\nIt is possible to monitor for crashes of the Nginx worker (`worker process \u2026 exited on signal` in the error log). However, this is not a high-fidelity indicator of successful remote code execution but rather an indication of exploitation attempts. Further checks in the process creation logs are necessary.\n\n## Mitigation\n\nWhen updating is not immediately possible, disabling HTTP/2 on exposed listeners (by removing the `http2` from the `listen` directives, or set `http2 off;`) mitigates the vulnerabilities CVE-2026-123007 and CVE-2026-123633 [1].\n\n\n# References\n\n[1] <https://xint.io/blog/nginx2root-remote-code-execution>\n\n[2] <https://my.f5.com/manage/s/article/K000164058>\n\n[3] <https://nginx.org/en/security_advisories.html>\n\n",
    "content_html": "<p><em>History:</em></p><ul><li><em>18/11/2026 --- v1.0 -- Initial publication</em></li></ul><h2 id=\"summary\">Summary</h2><p>On 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process [1, 2]. </p><p>While researchers managed to successfully demonstrate the use of CVE-2026-123007 [1], no exploitation in the wild has been reported yet.</p><p>It is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances. </p><h2 id=\"technical-details\">Technical Details</h2><p>The vulnerability <strong>CVE-2026-123007</strong>, with a CVSS score of 8.1, is an integer overflow in HTTP/2 flow control which causes an out-of-bounds write on the heap. The only precondition is HTTP/2 enabled on a listening port.</p><p>The vulnerability <strong>CVE-2026-123633</strong>, with a CVSS score of 8.1, is a use-after-free flaw occurring when connection draining closes an active HTTP/2 connection while NGINX connects to an upstream server. HTTP/2 should be enabled and requests should be forwarded to an upstream server.</p><p>The vulnerability <strong>CVE-2026-121810</strong>, with a CVSS score of 8.1, is a use-after-free flaw occurring when a QUIC connection is drained during stream creation and upstream connection. HTTP/3 should be enabled and requests should be forwarded to an upstream server.</p><p>The vulnerability <strong>CVE-2026-123634</strong>, with a CVSS score of 8.1, is a use-after-free flaw occurring in the processing of the DNS resolver waiting list. a <code>resolver</code> must be set, a <code>proxy_pass</code> destination built from request data, and <code>mirror</code> with <code>mirror_request_body off</code> should be configured.</p><p>The vulnerability <strong>CVE-2026-113425</strong>, with a CVSS score of 8.1, is a use-after-free occurring when the client closes the connection during the <code>auth_http</code> authentication lookup. A mail proxy must be configured with <code>proxy on</code> and <code>auth_http</code>.</p><p>All five vulnerabilities can lead to unauthenticated code execution with the privileges of the NGINX worker process [1]. </p><h2 id=\"affected-products\">Affected Products</h2><p>The following products and versions are affected by one or more of the above vulnerabilities:</p><ul><li>NGINX Open Source (mainline) from version 1.9.5 to 1.31.8 (range depends on the vulnerability, see Technical Details) [1]. Refer to the vendor advisory for the information on fixed versions [2].</li><li>NGINX Open Source (stable) versions 1.30.x, including the current stable version 1.30.6 [1, 3]. Refer to the vendor advisory for the information on fixed versions [2].</li><li>NGINX Plus from version 37.0.0 to 37.0.7.1, and 37.1.0 to 37.2.0.1. The versions R34, R35 and R36 are also affected [2]. Refer to the vendor advisory for the information on fixed versions [2].</li></ul><h2 id=\"recommendations\">Recommendations</h2><p>CERT-EU recommends updating vulnerable instance as soon as possible, prioritising internet-facing devices.</p><h3 id=\"compromise-assessment\">Compromise assessment</h3><p>It is possible to monitor for crashes of the Nginx worker (<code>worker process \u2026 exited on signal</code> in the error log). However, this is not a high-fidelity indicator of successful remote code execution but rather an indication of exploitation attempts. Further checks in the process creation logs are necessary.</p><h3 id=\"mitigation\">Mitigation</h3><p>When updating is not immediately possible, disabling HTTP/2 on exposed listeners (by removing the <code>http2</code> from the <code>listen</code> directives, or set <code>http2 off;</code>) mitigates the vulnerabilities CVE-2026-123007 and CVE-2026-123633 [1].</p><h2 id=\"references\">References</h2><p>[1] <a rel=\"noopener\" target=\"_blank\" href=\"https://xint.io/blog/nginx2root-remote-code-execution\">https://xint.io/blog/nginx2root-remote-code-execution</a></p><p>[2] <a rel=\"noopener\" target=\"_blank\" href=\"https://my.f5.com/manage/s/article/K000164058\">https://my.f5.com/manage/s/article/K000164058</a></p><p>[3] <a rel=\"noopener\" target=\"_blank\" href=\"https://nginx.org/en/security_advisories.html\">https://nginx.org/en/security_advisories.html</a></p>",
    "licence": {
        "title": "Creative Commons Attribution 4.0 International (CC-BY 4.0)",
        "link": "https://creativecommons.org/licenses/by/4.0/",
        "restrictions": "https://cert.europa.eu/legal-notice",
        "author": "The Cybersecurity Service for the Union institutions, bodies, offices and agencies"
    }
}