---
title: "NGINX and Apache HTTP/2 flaws: what to ask your WordPress host"
description: "NGINX announced fixes for two HTTP/2 vulnerabilities on November 18, 2026. WordPress updates cannot install them. Ask your host to confirm it is installed."
url: "https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/"
lang: "en"
published: "2026-11-18"
modified: "2026-11-18"
author: "Cal Hewitt"
tags: ["website-security","wordpress","web-hosting"]
image: "https://webleveling.com/og/blog-nginx-apache-http2-vulnerabilities-wordpress-hosting.jpg"
alternates:
  es: "https://webleveling.com/es/blog/vulnerabilidades-http2-nginx-apache-pregunte-a-su-hosting.md"
---

# NGINX and Apache HTTP/2 flaws: what to ask your WordPress host

NGINX announced fixes for two HTTP/2 vulnerabilities on November 18, 2026. WordPress updates cannot install them. Ask your host to confirm it is installed.

![A plant nursery owner in an apron stands between greenhouse benches before opening on a grey overcast dawn, looking down at a phone held at an angle, trays of seedlings and wet gravel around them.](https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/http2-featured.jpg)

NGINX announced fixed versions 1.30.7 and 1.31.9 for two HTTP/2 flaws on November 18, 2026, and Apache fixed one it rates critical in 2.4.71 on November 11, 2026. NGINX and Apache are the web-server software that answers your visitors' requests before WordPress runs. HTTP/2 is the newer version of the language browsers and servers use to exchange pages.

These fixes belong to your host, not to WordPress. [Wordfence](https://www.wordfence.com/blog/2026/11/nginx-http2-vulnerabilities-wordpress/), a WordPress security vendor, states that updating WordPress, a plugin, a theme or Wordfence itself will not patch NGINX, because the web server handles HTTP/2 before a request reaches PHP or WordPress. On November 18, 2026, [CERT-EU](https://cert.europa.eu/publications/security-advisories/2026-022/) reported no exploitation in the wild, although researchers had demonstrated one of the NGINX flaws, CVE-2026-123007.

What matters first is who controls your server. On managed or shared hosting, the host installs the fix and you ask for written confirmation. On a server you run yourself, you or your administrator installs it. The sections below cover both, starting with what was fixed.

**Key Takeaways**

**Three flaws, three fixes**

NGINX 1.30.7 and 1.31.9 fix CVE-2026-123007 and CVE-2026-123633, and Apache 2.4.71 fixes CVE-2026-119618.

**The server needs the patch**

A WordPress, plugin or security plugin update cannot install a web-server fix, so the host or server administrator does it.

**No exploitation reported yet**

As of November 18, 2026, CERT-EU reports none in the wild, so a warning email is a reason to check, not a sign of a break-in.

**Ask in writing**

Managed or shared hosting customers send one written request; self-managed owners install the fixed version and restart.

## Know what was fixed, and who has to install it

The two NGINX flaws and the Apache flaw all sit in HTTP/2 handling. NGINX lists CVE-2026-123007 as memory corruption in HTTP/2 flow control and CVE-2026-123633 as a use-after-free in HTTP/2, which is a memory error. Apache lists CVE-2026-119618 as heap corruption in its \`mod\_http2\` module. The affected versions, fixed versions and ratings are in the table, each as the source gives it.

The three flaws, as each source rates them

| CVE | Software and affected versions | Fixed in | Date | Rating |
| --- | --- | --- | --- | --- |
| CVE-2026-123007 | NGINX 1.9.5 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) | Announced November 18, 2026 | NGINX: major. CERT-EU: CVSS 8.1. F5: Critical, 9.2 under CVSS v4.0 |
| CVE-2026-123633 | NGINX 1.19.7 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) | Announced November 18, 2026 | NGINX: medium. CERT-EU: CVSS 8.1 |
| CVE-2026-119618 | Apache HTTP Server 2.4.55 to 2.4.70 | 2.4.71 | Released November 11, 2026 | Apache: critical |

The [NGINX security advisories](https://nginx.org/en/security_advisories.html) list both NGINX flaws, and the same release fixes other flaws as well. [F5](https://my.f5.com/manage/s/article/K000163926), which owns NGINX, gives CVE-2026-123007 a High 8.1 under CVSS 3.1 and a Critical 9.2 under CVSS 4.0, and lists NGINX Plus fixes at 37.3.0.1 and 37.0.8.1. The [Apache HTTP Server vulnerabilities page](https://httpd.apache.org/security/vulnerabilities_24.html) lists the Apache fix and its critical rating.

Dates to keep straight

1.  1

    November 11, 2026

    Apache HTTP Server 2.4.71 is released with the fix for CVE-2026-119618.

2.  2

    November 18, 2026

    NGINX announces 1.30.7 and 1.31.9, fixing CVE-2026-123007 and CVE-2026-123633.

3.  3

    November 18, 2026

    CERT-EU reports that researchers demonstrated CVE-2026-123007 and that no exploitation in the wild has been reported.

## Skip the plugin updates that cannot reach the server

Your site runs in layers. A visitor's request reaches the web server first, then PHP, then WordPress, then your plugins. A WordPress update changes the upper layers. A fix for NGINX or Apache has to be installed on the machine that runs the web server, which is why only whoever controls that machine can apply it.

Plugin updates still matter for plugin flaws, and our guide to [checking WordPress plugins for urgent security updates](https://webleveling.com/blog/check-wordpress-plugins-for-urgent-security-updates/) covers that separate job. Wordfence adds that a plugin firewall runs at the PHP layer and a scan cannot confirm whether the server is patched. So, leave the plugin list alone for this warning and put your effort into the host's answer.

![A plant nursery owner in an apron waters seedlings beside the open front of a small street-side garden shop at dusk, warm shop light spilling onto the sidewalk where a customer is walking in.](https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/http2-nursery-front.jpg)

Visitors reach the server first, just as customers reach the shop door before the owner.

## Learn in ten minutes whether your site is affected

Your site is affected when its web server runs a version in the table above and HTTP/2 is turned on. For CVE-2026-123007, CERT-EU states that the only precondition is HTTP/2 enabled on a listening port. You can learn the two facts without logging in to a server, because the people who control it can tell you.

Start with your hosting control panel and your host's status or security page, which sometimes name the server software. A response header that says nginx or Apache is a clue. It is not proof, because a proxy or content delivery network (CDN) in front of your site can hide the server that actually holds your files. If those places give no answer, ask your host in writing.

**Ten-minute owner check**

**Find who controls your server**

Check your hosting plan: managed or shared hosting means the host controls it, a VPS or your own machine means you do.

**Look at the panel and status page**

Your control panel or the host's status page may name the web server and show maintenance notices.

**Treat headers as a clue**

A header showing nginx or Apache can point to a proxy or CDN rather than the server holding your site.

**Send the written request**

Ask the host the questions in the next section and keep the ticket.

**Confirm your backups ran**

Check the date of your most recent backup before any server change.

Some sites sit behind a CDN, and a CDN's HTTP/2 setting can differ from the setting on the server behind it. The question for your host is about the origin server, the one that holds your site's files.

![A hand-lettered card taped to the door of a plant greenhouse in late afternoon sun reads "Ask the host first", the tape slightly curled and the card creased at one corner.](https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/http2-ask-the-host-card.jpg)

One written question to the right person settles more than a week of plugin updates.

## Get a written answer when your host runs the server

On managed or shared hosting, the host controls the web server, so the host installs the fix and restarts the service. Your part is one clear written request. A support ticket may settle the whole matter, and this warning alone is no reason to move hosts, buy a new security plugin or pay for an audit.

Copy the request into your host's ticket form, and add your domain name. Ask the host to name the server software on your plan, the exact version or vendor package, whether HTTP/2 is turned on for your site, whether the fixes for the NGINX and Apache flaws are installed, and when the service was last restarted or the container recreated.

What to ask your host, and what a useful answer includes

| Ask | A useful answer includes |
| --- | --- |
| Which web server handles my site? | NGINX, Apache HTTP Server or another server, named |
| What exact version or package is running? | A version number, or the vendor package name and build |
| Is HTTP/2 on for my site? | Yes or no, for the origin server |
| Is the fix installed for CVE-2026-123007, CVE-2026-123633 or CVE-2026-119618? | The CVE numbers, the fixed version or package, and the date installed |
| When was the service restarted or the container recreated? | A date and time |

The restart question matters because a patched package keeps running the old code until the service restarts. Some systems also carry a fix in a package whose version number looks older than the upstream one, so ask for the CVE status as well as the number. The [choosing web hosting guide](https://webleveling.com/blog/choosing-web-hosting-for-a-small-business/) and the post on [whether managed WordPress hosting helps SEO](https://webleveling.com/blog/does-managed-wordpress-hosting-help-seo/) explain what each hosting type covers.

![A plant nursery owner sits in the cab of a parked pickup at midday with the door open and a phone held to one ear, a paper pad on the steering wheel, greenhouses and bright sky behind.](https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/http2-owner-calls-host.jpg)

The call or ticket to the host is the whole task on managed or shared hosting.

## Patch or pause HTTP/2 when you run the server yourself

On a VPS (a rented virtual server), a dedicated machine or a container stack you manage, nobody else will install the fix, so you or your administrator does. Keep a current backup first. Then follow the vendors' steps, in this order.

1.  **Identify what is running**: Note the installed NGINX or Apache version or package, and whether HTTP/2 is active on the listener.
2.  **Install the fixed version**: NGINX Open Source 1.30.7 or 1.31.9, the F5 fix for your NGINX Plus branch, or Apache 2.4.71 or the operating system package that contains the fix.
3.  **Test the configuration, then restart or reload**: The old process keeps serving until the service restarts.
4.  **Recreate containers from patched images**: Pull an image with the fixed build and recreate the container.
5.  **Confirm the new process is serving traffic**: Check the running version afterward.

If patching cannot happen right away, CERT-EU says HTTP/2 can be turned off on exposed NGINX listeners as a temporary step, by removing \`http2\` from the listener or using \`http2 off;\`. That blocks the two NGINX HTTP/2 paths and removes HTTP/2 service, and it leaves the other flaws fixed in the same release open. Test the change and restart, and treat it as a bridge to patching.

CERT-EU also says worker crashes point to possible exploitation attempts, not proof of a successful break-in. If your logs show crashes or odd process activity, bring in a security professional rather than guessing.

## Keep a record that settles the question for good

When your host replies, save the ticket with your maintenance records. A reply that names the server, the fixed version or package, and the restart date answers the question completely. A generic "we are secure" reply leaves the question open, so write back and ask for the specifics again.

Paid help makes sense when the host cannot identify the server or its patch status, when your site runs on a VPS or container stack, when several sites share one server, when backups are uncertain, or when logs show crashes. Without those, a support ticket is usually the whole job, and our guide to [website maintenance costs](https://webleveling.com/blog/how-much-does-website-maintenance-cost/) shows what ongoing update coordination involves when you want it handled.

![Two people at a plant nursery on a bright morning load trays of flowers onto a wheeled cart in front of an open greenhouse, one laughing, with a hand-painted "Open" board leaning on the gate.](https://webleveling.com/blog/nginx-apache-http2-vulnerabilities-wordpress-hosting/http2-open-for-business.jpg)

A confirmed answer from the host lets Monday morning go back to selling plants.

**Quiz: Who fixes the NGINX and Apache HTTP/2 flaws?**

1. Which update installs the NGINX fix on a managed WordPress host?
   - A WordPress core update
   - A security plugin update
   - An update to the web server, installed by the host **(correct answer)**
   - A theme update
2. Which NGINX versions contain the fixes announced on November 18, 2026?
   - 1.9.5 and 1.19.7
   - 1.30.7 and 1.31.9 **(correct answer)**
   - 1.31.8 and 2.4.71
   - 1.30.6 and 1.31.0
3. As of November 18, 2026, what does CERT-EU report about exploitation?
   - Researchers demonstrated CVE-2026-123007, and no exploitation in the wild has been reported **(correct answer)**
   - Every WordPress site has been compromised
   - Apache sites were attacked first
   - Disabling HTTP/2 permanently is required

## Frequently Asked Questions About NGINX and Apache HTTP/2 Flaws on WordPress Hosting

**Does updating WordPress fix the NGINX HTTP/2 vulnerability?**

Updating WordPress, a plugin or a theme leaves the web server unchanged. The flaws are in NGINX and Apache, so the host or server administrator installs the fixed version and restarts the service.

**How do I know whether my site uses NGINX or Apache?**

Check your hosting control panel and the host's status page, and read a response header for nginx or Apache as a clue. A proxy or CDN can hide the origin server, so ask your host in writing for the server, version and HTTP/2 status.

**Which versions fix the NGINX flaws?**

NGINX Open Source 1.30.7 and 1.31.9 fix both CVE-2026-123007 and CVE-2026-123633. NGINX Plus customers use the fixed release from F5 for their branch.

**Is the Apache flaw fixed?**

Apache HTTP Server 2.4.71, released November 11, 2026, fixes CVE-2026-119618, which affects versions 2.4.55 through 2.4.70. A host may also carry the fix in an operating system package, so ask for the CVE status.

**Should I turn off HTTP/2 until my host patches?**

On a server you run yourself, CERT-EU says turning HTTP/2 off on exposed NGINX listeners is a temporary step. It leaves the other flaws fixed in the same release open, so patching remains the fix. On managed or shared hosting, leave server settings to the host unless it directs you.

**Does a Wordfence warning mean my site was hacked?**

A warning email points to a flaw in server software. As of November 18, 2026, CERT-EU reports no exploitation in the wild, so the sensible step is to get your host's written answer and confirm your backups.

## Final Thoughts

NGINX 1.30.7 and 1.31.9, announced on November 18, 2026, and Apache 2.4.71, released on November 11, 2026, fix these HTTP/2 flaws. The fix sits in the web server, so the host installs it on managed or shared hosting and you or your administrator installs it on a server you run. A written answer naming the server, the fixed version and the restart date closes the matter.

Once you have that answer, the warning has done its job. A saved ticket and a current backup are the habits worth keeping for the next notice.

If you would like help reading your host's reply, or handling the update on a server you manage, [Web Leveling](https://webleveling.com/) can do that through our [web hosting](https://webleveling.com/services/web-hosting/) and [website maintenance](https://webleveling.com/services/website-maintenance/) work. We work with small and medium businesses across the country and overseas. [Send us your host's reply](https://webleveling.com/contact/) and we will tell you what it means.

## Terms

Words used in this post

Tap a term to see what it means.

**NGINX.** Web-server software that answers visitors' requests for a site before WordPress runs.

**Apache HTTP Server.** Web-server software that does the same job as NGINX, also called Apache.

**HTTP/2.** A newer version of the language browsers and servers use to exchange web pages.

**CVE.** A public identification number for a known security flaw, such as CVE-2026-123007.

**CVSS score.** A severity score from 0 to 10 that a vendor or agency assigns to a flaw.

**Origin server.** The server that holds your site's files, behind any proxy or CDN.

**Backport.** A security fix added to an older version of a package without changing its version number to match the upstream release.

Share this article

[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwebleveling.com%2Fblog%2Fnginx-apache-http2-vulnerabilities-wordpress-hosting%2F)[Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwebleveling.com%2Fblog%2Fnginx-apache-http2-vulnerabilities-wordpress-hosting%2F)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwebleveling.com%2Fblog%2Fnginx-apache-http2-vulnerabilities-wordpress-hosting%2F&text=NGINX%20and%20Apache%20HTTP%2F2%20flaws%3A%20what%20to%20ask%20your%20WordPress%20host)[WhatsApp](https://wa.me/?text=NGINX%20and%20Apache%20HTTP%2F2%20flaws%3A%20what%20to%20ask%20your%20WordPress%20host%20https%3A%2F%2Fwebleveling.com%2Fblog%2Fnginx-apache-http2-vulnerabilities-wordpress-hosting%2F)[Email](mailto:?subject=NGINX%20and%20Apache%20HTTP%2F2%20flaws%3A%20what%20to%20ask%20your%20WordPress%20host&body=https%3A%2F%2Fwebleveling.com%2Fblog%2Fnginx-apache-http2-vulnerabilities-wordpress-hosting%2F)

- [FBI SEO poisoning on WordPress: how to check if yours was used](https://webleveling.com/blog/fbi-seo-poisoning-hacked-wordpress-ransomware/): On November 16, 2026, the FBI said hacked WordPress sites were used in SEO poisoning. Check Search Console and search your site for pages you did not write.
- [WordPress 7.1.4: update your site and confirm the version](https://webleveling.com/blog/wordpress-7-1-4-security-release/): WordPress 7.1.4 is a security release that WordPress.org recommends updating immediately. Back up, then check your version under Dashboard and Updates.
- [Fake Cloudflare verification WordPress: what to check now](https://webleveling.com/blog/wordpress-fake-cloudflare-check-php-backdoor/): Look for an unfamiliar administrator, a plugin named Web Media Optimizer, or wmedia-recovery.php in mu-plugins. Those are the reported signs of this attack.
