Security advisory · 19 November 2026

Zimbra nginx vulnerability CVE-2026-123007: check and fix.

Your Zimbra proxy is probably exposed to the critical nginx HTTP/2 flaw known as NGINX2Root. Here is how to check it and how to switch HTTP/2 off until Zimbra ships a fixed build.

CVE-2026-123007 NGINX2Root: critical nginx HTTP/2 remote code execution, CVSS 9.2. Zimbra 10.1.21 with zimbra-nginx 1.24.0 is affected. Fixed in nginx 1.30.7 and 1.31.9.

On 18 November 2026 a critical flaw in nginx's HTTP/2 code was disclosed: CVE-2026-123007, rated 9.2 (Critical) under CVSS 4.0. An integer underflow in HTTP/2 flow control lets a remote, unauthenticated attacker corrupt heap memory. That can leak data, crash the server, or lead to code execution with the privileges of the nginx worker. Researchers have shown a working exploit in the lab. No attacks in the wild have been reported so far.

Test first. Run every step below on a dev or staging server first. Move to production only after you have confirmed that webmail, sign-in and attachments still work.

Who is affected

  • nginx open source 1.9.5 – 1.30.6 and 1.31.0 – 1.31.8, when HTTP/2 is enabled. Servers that speak only HTTP/1.1 are not affected.
  • Fixed upstream in nginx 1.30.7 (stable) and 1.31.9 (mainline).
  • Zimbra 10.1.21, the latest patch (24 September 2026), ships zimbra-nginx 1.24.0-1zimbra8.8b8, which is inside the vulnerable range. Its default HTTPS proxy templates enable HTTP/2.
  • Zimbra has not released a fixed zimbra-nginx yet. Updating your operating system's nginx package won't help, because Zimbra runs its own binary: /opt/zimbra/common/sbin/nginx.

How to check

1. Version

su - zimbra -c "/opt/zimbra/common/sbin/nginx -v"

2. Is HTTP/2 configured?

grep -rn "http2" /opt/zimbra/conf/nginx/templates/

On a default install this shows listen ... ssl http2; lines in nginx.conf.web.https.template and nginx.conf.web.https.default.template.

3. Does the server actually speak HTTP/2?

openssl s_client -connect mail.yourdomain.com:443 -alpn h2 </dev/null 2>&1 | grep ALPN

If you see ALPN protocol: h2, you are exposed. If you see No ALPN negotiated, HTTP/2 is off.

Mitigation: turn HTTP/2 off

Zimbra 10.1.x uses nginx 1.24, where http2 is a parameter on the listen line. The http2 off; directive only exists from nginx 1.25.1, so you have to remove the parameter instead. Edit the templates, not the includes: Zimbra rebuilds the files in includes/ from the templates.

Step 1. Back up the templates (as root)

cd /opt/zimbra/conf/nginx/templates
mkdir -p /root/nginx-tpl-backup && cp -a ./*.template /root/nginx-tpl-backup/
ls /root/nginx-tpl-backup | wc -l

The last command should print a number above zero.

Step 2. Remove http2 from the listen lines

Zimbra's listen lines start with a template variable, for example ${core.ipboth.enabled}listen. A pattern that expects the line to start with listen silently changes nothing, so match listen anywhere on the line:

grep -rl "http2" . | xargs -r sed -i -E '/listen/ s/[[:space:]]+http2([[:space:]]*;)/\1/'
grep -rn "http2" .

The second command should print nothing.

Step 3. Regenerate the config and restart the proxy

su - zimbra -c "/opt/zimbra/libexec/zmproxyconfgen && zmproxyctl restart"

Step 4. Verify

grep -rn "http2" /opt/zimbra/conf/nginx/includes/
openssl s_client -connect mail.yourdomain.com:443 -alpn h2 </dev/null 2>&1 | grep ALPN

The first command should print nothing, and the second should now say No ALPN negotiated. Webmail keeps working normally over HTTP/1.1, and users won't notice a difference.

Rolling back

Copy the files from /root/nginx-tpl-backup/ back into /opt/zimbra/conf/nginx/templates/ and run Step 3 again.

Gotchas

  • Don't run nginx -T as root on Zimbra. It changes the owner of /opt/zimbra/data/tmp/nginx, and then large uploads fail with 500 errors. If that already happened, run chown -R zimbra:zimbra /opt/zimbra/data/tmp/nginx.
  • If a load balancer, reverse proxy or CDN sits in front of Zimbra, check HTTP/2 there too.
  • A future Zimbra patch may overwrite these templates. Run the ALPN check again after every upgrade.

The permanent fix

Install Zimbra's updated zimbra-nginx as soon as it is released. Turning HTTP/2 off blocks only this CVE. The same nginx release fixes four more flaws, and only the patched binary covers those.

Looking for a modern alternative to Zimbra? Mailflew is an open-source-based workspace offered as a managed service: mail, chat, calendar, drive and meetings in one secure app on your own domain, with an AI assistant built in. We also move your mail across from Zimbra, hosted in India, the USA or Europe. See why teams choose Mailflew over Zimbra or talk to us.

Frequently asked questions

Is Zimbra 10.1.21 vulnerable to CVE-2026-123007?

Yes, when HTTP/2 is enabled, which it is in Zimbra's default HTTPS proxy templates. Zimbra 10.1.21 ships zimbra-nginx 1.24.0, inside the affected range of nginx 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8.

How do I check if my Zimbra server is exposed?

Run the openssl s_client ... -alpn h2 check above. If it prints ALPN protocol: h2, HTTP/2 is on and the server is exposed.

How do I disable HTTP/2 in Zimbra?

Back up /opt/zimbra/conf/nginx/templates, remove the http2 parameter from the listen lines in nginx.conf.web.https.template and nginx.conf.web.https.default.template, then run zmproxyconfgen and zmproxyctl restart as the zimbra user (Steps 1 to 4 above).

Will updating the operating system's nginx package fix Zimbra?

No. Zimbra runs its own nginx binary at /opt/zimbra/common/sbin/nginx, so only an updated zimbra-nginx package from Zimbra fixes it.

Sources

← All posts

Take control of your communication

Get started with Mailflew today. We'll set it up on your servers, under your domain, with your rules.