Tag: HTTP/2

  • Apache HTTP Server 2.4.71: Patch mod_http2 CVE-2026-119618

    Apache HTTP Server 2.4.71: Patch mod_http2 CVE-2026-119618

    Apache HTTP Server 2.4.71 security update graphic: orange shield with a keyhole and the mod_http2 fix CVE-2026-119618

    Introduction

    Apache HTTP Server 2.4.71, released on November 11, 2026, fixes three vulnerabilities, including CVE-2026-119618, a critical flaw in mod_http2 that the Apache project says can lead to remote code execution. Apache httpd still powers many WordPress, PHP and shared hosting servers, and HTTP/2 is common on modern sites. If you run Apache 2.4.55 or later with HTTP/2, plan the update now.

    This article summarizes the official Apache advisory and Linux distribution notices, shows how to check your server, and explains how to update. It contains no exploit details.

    Key Facts: Apache HTTP Server 2.4.71 at a Glance

    • What: Apache HTTP Server 2.4.71 (November 11, 2026) fixes CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163.
    • Most serious: CVE-2026-119618, a race condition in mod_http2 (assign_headers()) that can lead to remote code execution. The Apache project rates it critical.
    • Affected: Apache httpd 2.4.55 to 2.4.70 with mod_http2, and standalone mod_h2 2.0.8 to 2.0.42. Distribution packages with older version numbers can also be affected.
    • Severity: critical (Apache project). CVSS v3.1 8.1 from CISA’s enrichment in NVD; Ubuntu rates it “High” priority.
    • Exploitation: none reported. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the CISA KEV catalog (version 2026.11.18).
    • Action: upgrade to 2.4.71 or your distribution’s patched package, then restart Apache.

    What Does Apache HTTP Server 2.4.71 Fix?

    Apache HTTP Server 2.4.71 fixes one critical, one important and one low-severity issue, according to the Apache httpd security page.

    CVEModuleIssueApache severityCVSS v3.1 (CISA ADP)
    CVE-2026-119618mod_http2Race condition in assign_headers(), heap corruption and possible remote code executionCritical8.1
    CVE-2026-106023mod_mdNULL pointer dereference that crashes a child processImportant7.5
    CVE-2026-109163mod_vhost_aliasOne-byte stack buffer overwrite (after CVE-2026-63292)Low5.9

    The Apache project does not publish CVSS scores. The scores above come from CISA’s Authorized Data Publisher entries in NVD. NVD itself had not finished analyzing CVE-2026-106023 and CVE-2026-109163 when we checked.

    Which Apache Versions Are Affected?

    Upstream Apache httpd 2.4.70 and earlier are affected, but the exact range depends on the CVE and on how your distribution packages mod_http2.

    CVEAffected (Apache project)Fixed in
    CVE-2026-1196182.4.55 to 2.4.70; mod_h2 2.0.8 to 2.0.422.4.71
    CVE-2026-1060232.4.30 to 2.4.702.4.71
    CVE-2026-1091632.4.69 to 2.4.702.4.71

    NVD’s descriptions give slightly narrower ranges for the two lower-severity CVEs (ending at 2.4.69). We follow the Apache project’s page.

    Why can older distribution versions be affected?

    Distributions often backport newer mod_http2 code into older httpd packages. Ubuntu’s security notes say exactly this for CVE-2026-119618, and Ubuntu lists its 22.04 package (based on 2.4.52) as affected and fixed. So check your vendor’s tracker, not just the upstream version number.

    DistributionFixed package (CVE-2026-119618)
    Ubuntu 26.04 LTS2.4.66-2ubuntu2.8
    Ubuntu 24.04 LTS2.4.58-1ubuntu8.19
    Ubuntu 22.04 LTS2.4.52-1ubuntu4.27
    Ubuntu 20.04 LTS2.4.41-4ubuntu3.23+esm11 (Ubuntu Pro)
    Debian 13 (trixie)2.4.71-1~deb13u1 (DSA-6620-1)
    Debian 12 (bookworm)2.4.71-1~deb12u1 (DLA-4902-1)

    Ubuntu lists 18.04 and older as not affected. For Red Hat, AlmaLinux and other platforms, check the vendor pages linked from the NVD record.

    What Is the Security Impact?

    The worst case is remote code execution through mod_http2, while the other two issues mainly crash Apache child processes.

    What can CVE-2026-119618 do?

    The Apache advisory describes a concurrency bug: shared resources are used without proper synchronization in mod_http2’s assign_headers() function. This can corrupt heap memory and, according to the advisory, lead to remote code execution. CISA’s vector marks it as network-reachable without authentication but with high attack complexity. That fits a race condition, which is hard but not impossible to win.

    What about mod_md and mod_vhost_alias?

    CVE-2026-106023 lets a request crash an Apache child process when mod_md, Apache’s built-in ACME certificate module, is in use. CVE-2026-109163 is a one-byte stack overwrite in mod_vhost_alias that affects only 2.4.69 and 2.4.70. Ubuntu’s notice says it could possibly lead to code execution.

    How Do I Check Whether Apache HTTP Server 2.4.71 Is Needed?

    Check the installed version and package release, then confirm whether mod_http2 is loaded and HTTP/2 is enabled.

    How do I check my Apache version?

    apache2 -v          # Debian/Ubuntu
    httpd -v            # RHEL/AlmaLinux/Fedora
    dpkg -l apache2     # full Debian/Ubuntu package version
    rpm -q httpd        # full RPM package version

    Compare the full package version with the table above or your vendor’s tracker. On managed or shared hosting, ask your provider whether USN-9090-1, DSA-6620-1 or an equivalent fix is installed.

    How do I check whether HTTP/2 is enabled?

    apache2ctl -M 2>/dev/null | grep -E "http2|md_module|vhost_alias"
    grep -rniE "^\s*Protocols" /etc/apache2 /etc/httpd 2>/dev/null

    If http2_module is loaded and a Protocols line includes h2 or h2c, treat CVE-2026-119618 as urgent.

    How Do I Fix These Apache Vulnerabilities?

    Install Apache HTTP Server 2.4.71 or your distribution’s patched package, then restart Apache.

    1. Back up first. Copy your Apache configuration and, for WordPress, follow our guide on how to back up WordPress.
    2. Update the package. On Ubuntu and Debian run sudo apt update && sudo apt install --only-upgrade apache2. On RPM-based systems use sudo dnf upgrade httpd.
    3. Check and restart. Run apachectl configtest, then restart Apache so all child processes use the fixed code.
    4. Check standalone mod_h2. The advisory lists mod_h2 2.0.8 to 2.0.42 as affected; check the mod_h2 project for a fixed release.
    5. Rebuild containers based on httpd or distribution images.

    What if I cannot update right away?

    The Apache advisory does not list a workaround, so the update is the fix. If your site does not need HTTP/2, removing h2 and h2c from Protocols takes mod_http2 out of the request path. This is our assessment, not vendor guidance, and it does not address CVE-2026-106023 or CVE-2026-109163.

    Additional Security Recommendations

    Applying Apache HTTP Server 2.4.71 is the main defense. These habits limit the damage from the next web server bug:

    FAQ

    Is CVE-2026-119618 being exploited?

    No exploitation has been reported as of November 20, 2026. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the KEV catalog (version 2026.11.18). Public exploit availability is unknown.

    Am I affected if I run Apache 2.4.52 on Ubuntu 22.04?

    Yes, unless you have package 2.4.52-1ubuntu4.27 or later. Ubuntu backported newer mod_http2 code, so its 2.4.52 package is affected even though upstream 2.4.52 is older than 2.4.55.

    Do I need Apache HTTP Server 2.4.71 if HTTP/2 is disabled?

    Yes, still update. CVE-2026-119618 needs mod_http2, but the mod_md and mod_vhost_alias fixes also matter, and a later configuration change could enable HTTP/2.

    Is nginx affected by these CVEs?

    No. These CVEs are specific to Apache httpd modules. Nginx had its own security release on November 18, 2026.

    Conclusion

    Apache HTTP Server 2.4.71 closes a critical mod_http2 race condition and two smaller bugs. Check your package version against your vendor’s tracker, install Apache HTTP Server 2.4.71 or the patched package, and restart Apache today.

    References

    All links below returned HTTP 200 when checked on November 20, 2026.

    Related Articles

    Last Verified: November 20, 2026. Prepared by SafeWebAcademy from the official Apache HTTP Server advisory, NVD records and Linux distribution security notices linked above. This is not an official Apache Software Foundation publication. Security details can change, so check the linked advisories for updates.

  • Nginx Security Update: 1.30.7 and 1.31.9 Fix 10 CVEs

    Nginx Security Update: 1.30.7 and 1.31.9 Fix 10 CVEs

    Nginx security update graphic: green shield with a keyhole and the fixed versions 1.30.7 stable and 1.31.9 mainline

    Introduction

    This nginx security update, released on November 18, 2026 as nginx 1.30.7 (stable) and 1.31.9 (mainline), fixes 10 vulnerabilities. Three are rated “major” by the nginx project, and F5 scores five of them 9.2 (critical) in CVSS v4.0. The affected features include HTTP/2, HTTP/3, the mail proxy, the resolver and several stream (TCP/TLS) modules.

    Nginx fronts many PHP, Node.js and Python sites, so most admins should check their version this week. This article summarizes the official advisories and shows how to check and update, without exploit details.

    Key Facts: Nginx Security Update at a Glance

    • What: nginx 1.30.7 and 1.31.9 (released November 18, 2026) fix 10 CVEs.
    • Most serious: CVE-2026-123007 (HTTP/2 flow control memory corruption), CVE-2026-118899 (infinite loop over TLS 1.3) and CVE-2026-113425 (mail proxy use-after-free), all rated “major” by nginx.org.
    • Affected: nginx before 1.30.7 (stable) and 1.31.9 (mainline). Most issues go back many years, and the legacy 1.28 and older branches have no fixed release.
    • Severity: five CVEs score 9.2 in CVSS v4.0 (8.1 in CVSS v3.1), as assigned by F5 as the CVE Numbering Authority.
    • Exploitation: none reported. CISA’s SSVC assessment in NVD lists exploitation as “none” (November 18, 2026), and none of the CVEs is in the CISA KEV catalog (version 2026.11.18).
    • Action: upgrade to nginx 1.30.7 or 1.31.9 (or your vendor’s patched package), then restart nginx.

    Nginx Security Update Overview: What Does It Fix?

    The nginx security update fixes memory-safety bugs, a denial-of-service loop and three validation bypasses. Severity comes from nginx.org; CVSS scores come from F5 as published in NVD.

    CVEIssuenginx.org severityCVSS v4.0 / v3.1 (F5)Vulnerable versions
    CVE-2026-123007HTTP/2 flow control memory corruptionMajor9.2 / 8.11.9.5 to 1.31.8
    CVE-2026-118899Infinite loop reading the request body over TLS 1.3Major8.7 / 7.51.13.0 to 1.31.8
    CVE-2026-113425Mail proxy use-after-freeMajor9.2 / 8.10.5.33 to 1.31.8
    CVE-2026-123634Resolver use-after-freeMedium9.2 / 8.10.6.18 to 1.31.8
    CVE-2026-121810HTTP/3 use-after-freeMedium9.2 / 8.11.25.0 to 1.31.8
    CVE-2026-123633HTTP/2 use-after-free when proxyingMedium9.2 / 8.11.19.7 to 1.31.8
    CVE-2026-120967Stream SNI bypass of client certificate checksMedium6.3 / 4.81.25.5 to 1.31.8
    CVE-2026-125283Buffer overflow with alias and try_filesMinor6.9 / 5.30.9.6 to 1.31.8
    CVE-2026-120993NULL pointer dereference with PROXY protocol v2Minor6.9 / 5.31.31.4 to 1.31.8
    CVE-2026-123640Insufficient validation in stream ssl_prereadMinor6.9 / 5.31.15.2 to 1.31.8

    NVD has analyzed eight of these CVEs; CVE-2026-120993 and CVE-2026-120967 were still “Received” when we checked.

    Which Nginx Versions Are Affected?

    Every nginx release before 1.30.7 (stable) and 1.31.9 (mainline) is affected by at least one issue.

    BranchFixed inNotes
    1.31 mainline1.31.9Fixes all 10 CVEs, including mainline-only CVE-2026-120993
    1.30 stable1.30.7Fixes the 9 CVEs that affect the stable branch
    1.28 and older (legacy)No fixInside the vulnerable ranges; upgrade to 1.30.7 or 1.31.9

    According to the CPE data in NVD, F5’s NGINX Plus, NGINX Ingress Controller and NGINX Gateway Fabric are also affected. Check F5’s advisories if you run them.

    What Is the Security Impact?

    The worst case is a crashed nginx worker or, under extra conditions, code execution. Each issue only matters if you use the related feature.

    What can the HTTP/2, HTTP/3 and resolver bugs do?

    According to the F5 descriptions in NVD, CVE-2026-123007 can overflow the HTTP/2 flow control window and corrupt worker memory. CVE-2026-123633 affects HTTP/2 when nginx proxies requests and a worker runs low on worker_connections. CVE-2026-121810 is a similar use-after-free in HTTP/3. CVE-2026-123634 needs proxying with variables in the upstream name plus an SSI or mirror subrequest that resolves the same name.

    For all four, F5 says a remote attacker can crash a worker. Code execution is possible on systems where ASLR is disabled or can be bypassed.

    What about the denial-of-service and stream issues?

    CVE-2026-118899 affects listen ... ssl servers with TLS 1.3. A crafted connection can trap a worker in an endless loop while it reads a request body, so the worker stops serving clients. CVE-2026-113425 only affects the mail proxy. The remaining issues are narrower:

    • CVE-2026-120967: client certificate checks can be bypassed in a non-default stream server with ssl_verify_client on.
    • CVE-2026-123640: a crafted ClientHello can forge ssl_preread variables and change server selection.
    • CVE-2026-125283: try_files with alias and a map variable can crash a worker.
    • CVE-2026-120993: PROXY protocol v2 with dynamic certificate loading can crash a worker (mainline only).

    How Do I Check Whether the Nginx Security Update Applies to Me?

    Check your nginx version first, then look for the features named in the advisories.

    How do I check my nginx version?

    Run this on every server and inside every container image:

    nginx -v
    nginx -V 2>&1 | tr ' ' '\n' | grep -E "http_v2|http_v3|mail|stream"

    Anything below 1.30.7 on the stable branch or below 1.31.9 on mainline is affected. Linux distributions often backport fixes without changing the version number, so also check your vendor’s security tracker.

    How do I find the risky configuration?

    Dump the full configuration and search for the features involved:

    nginx -T 2>/dev/null | grep -nE "http2|quic|http3|mail|resolver|ssl_preread|ssl_verify_client|proxy_protocol|try_files|alias"

    If HTTP/2 or HTTP/3 is enabled on a public listener, treat this nginx security update as urgent. The same applies if you run nginx as a mail proxy.

    How Do I Fix These Nginx Vulnerabilities?

    Install nginx 1.30.7 or 1.31.9, or your vendor’s patched package, and restart nginx.

    1. Back up your configuration. Copy /etc/nginx before updating. Our Ubuntu server backup guide covers the basics.
    2. Upgrade. Use your package manager, the official nginx.org packages or a rebuilt container base image. Source tarballs are on the nginx download page.
    3. Test and restart. Run nginx -t, then restart nginx so every worker runs the new binary.
    4. Rebuild images that bundle nginx, and move off legacy 1.28 and older branches.

    What if I cannot upgrade right away?

    The nginx.org advisories list upgraded versions as the fix, and we found no official workaround. Until you can patch, general hardening reduces exposure: disable the mail proxy, HTTP/3 and stream features you do not use. This does not fix the HTTP/2 or TLS 1.3 issues, which only the upgrade does.

    Are there behavior changes in 1.31.9?

    Yes. Mainline 1.31.9 now rejects header lines without a colon and chunked request bodies with too much framing overhead. Test API clients and webhooks after upgrading. Stable 1.30.7 contains only the security fixes.

    Additional Security Recommendations

    Applying the nginx security update is the main defense. These habits also limit the damage from the next web server bug:

    FAQ

    Is the nginx security update urgent?

    Yes, if you use HTTP/2, HTTP/3 or TLS 1.3, which most modern sites do. Five issues score 9.2 in CVSS v4.0, and CVE-2026-118899 can stop a worker with a crafted connection.

    Are these nginx vulnerabilities being exploited?

    No exploitation has been reported as of November 20, 2026. CISA’s SSVC entries list exploitation as “none,” and none of the CVEs is in the KEV catalog (version 2026.11.18). Public exploit availability is unknown.

    Does this affect NGINX Plus or the Kubernetes ingress controller?

    According to NVD, F5’s NGINX Plus, NGINX Ingress Controller and NGINX Gateway Fabric are affected by some of these CVEs. Check F5’s advisories for their fixed versions. The community ingress-nginx project is separate, and we did not verify its status.

    Do I need to restart nginx after updating?

    Yes. Restart nginx so every worker runs the fixed binary, and redeploy any containers that bundle nginx.

    Conclusion

    The nginx security update in versions 1.30.7 and 1.31.9 closes 10 vulnerabilities, including HTTP/2 memory corruption and a TLS 1.3 denial of service. Check your version, upgrade, restart nginx and rebuild container images. Then review any HTTP/3, mail or stream features you do not need.

    References

    All links below returned HTTP 200 when checked on November 20, 2026.

    Related Articles

    Last Verified: November 20, 2026. Prepared by SafeWebAcademy from the official nginx.org advisories, nginx changelogs and NVD records linked above. This is not an official nginx or F5 publication. Security details can change, so check the linked advisories for updates.