As of 9:30am Eastern on November 19, 2026, Zimbra hasn’t publicly addressed the multiple CVEs around the recent Java4Shell and nginx2root http/2 exploits.
We are recommending to customers that they open a Sev-2 Support Case with Zimbra to ask for official guidance, and in the interim are sharing our own partial mitigations. In the interests of time, this blog post is leaner in the details we normally strive to include. Also, (because… lawyers), you assume all risk associated with applying the mitigations below and we make no representations nor warranty that applying the mitigations below will fully protect your Zimbra system.
Java4Shell – CVE-2026-114938
While Oracle patched Java on November 17, Zimbra runs an older version. However, we are given to understand that this exploit depends on your CPU’s capabilities — if you tell Java not to use the capability needed to perform the exploit, you are in a better place.
Check your CPU’s capabilities (as root):
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -x 'avx512vbmi'
If you get a hit for avx512vbmi, you are exposed. The mitigation is to modify localconfig, so first get the current value:
zmlocalconfig mailboxd_java_options
Copy the output to a text editor, and then modify it, like in this example below. The two changes are first, to add -XX:-UseBASE64Intrinsics at the end, and second, to make the output a change statement to the value of mailboxd_java_options.
Note that depending on the roles on your Zimbra server, and when you installed Zimbra, your list of attributes may be different. Therefore, DO NOT just copy and paste the example below!!
zmlocalconfig -e mailboxd_java_options='-server -Dhttps.protocols=TLSv1.2,TLSv1.3 -Djdk.tls.client.protocols=TLSv1.2,TLSv1.3 -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=${networkaddress_cache_ttl} -Dorg.apache.jasper.compiler.disablejsr199=true -XX:+UseG1GC -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=15 -XX:G1MaxNewSizePercent=45 -XX:-OmitStackTraceInFastThrow -verbose:gc -Xlog:gc*=info,safepoint=info:file=/opt/zimbra/log/gc.log:time:filecount=20,filesize=10m -Djava.security.egd=file:/dev/./urandom --add-opens java.base/java.lang=ALL-UNNAMED -Dcom.redhat.fips=false -Djava.net.preferIPv4Stack=true -XX:-UseBASE64Intrinsics'
Run YOUR VERSION of the above command as the Zimbra user, and then do a zmcontrol restart.
Five nginx CVEs – “nginx2root”
| CVE | Flaw | Exposed when | Fixed by removing HTTP/2? |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow-control heap overflow | HTTP/2 enabled | Yes |
| CVE-2026-123633 | HTTP/2 use-after-free | HTTP/2 plus proxying to a backend | Yes |
| CVE-2026-113425 | Mail proxy use-after-free | Mail proxy with proxy on and auth_http |
No |
| CVE-2026-121810 | HTTP/3 (QUIC) use-after-free | HTTP/3 plus proxying to a backend | No |
| CVE-2026-123634 | DNS resolver use-after-free | resolver, variable proxy_pass, and mirror |
No |
We speculate that the http/3 exploit does not apply to Zimbra, but that CVE-2026-113425 may, because Zimbra’s IMAP/POP proxy uses the proxy on plus auth_http setup. You could allow only trusted IPs, which for a public mail server means firewalling IMAP/POP where you can, until Zimbra provides patches. Or, just turn off IMAP. Again, we haven’t done a deep dive into the source code on this, so don’t have much more to share.
To turn off http/2 in Zimbra, you need to modify the relevant nginx template files and then restart Zimbra on your Proxy server(s) to have Zimbra rewrite the nginx configs using the modified templates.
1. Make a backup of your nginx template files:
ubuntu@webmail:~$ sudo su - root@webmail:~# su - zimbra zimbra@webmail:~$ cd /opt/zimbra/conf/nginx zimbra@webmail:~/conf/nginx$ cp -a templates templates.bak-$(date +%F)
2. Find the files that turn on http/2:
zimbra@webmail:~/conf/nginx$ grep -n 'http2' templates/*
templates/nginx.conf.web.https.default.template:32: ${core.ipboth.enabled}listen [::]:${web.https.port} ipv6only=off ssl http2;
templates/nginx.conf.web.https.default.template:33: ${core.ipv4only.enabled}listen ${web.https.port} ssl http2;
templates/nginx.conf.web.https.default.template:34: ${core.ipv6only.enabled}listen [::]:${web.https.port} ssl http2;
templates/nginx.conf.web.https.template:7: ${core.ipboth.enabled}listen ${vip}${web.https.port} ipv6only=off ssl http2;
templates/nginx.conf.web.https.template:8: ${core.ipv4only.enabled}listen ${vip}${web.https.port} ssl http2;
templates/nginx.conf.web.https.template:9: ${core.ipv6only.enabled}listen ${vip}${web.https.port} ssl http2;
zimbra@webmail:~/conf/nginx$
3. Remove the “http2” directive from the impacted files and check that http2 is gone-gone:
zimbra@webmail:~/conf/nginx$ sed -i '/listen/ s/[[:space:]]\+http2\b//' templates/nginx.conf.web.https.default.template templates/nginx.conf.web.https.template
zimbra@webmail:~/conf/nginx$ grep -n 'http2' templates/*
zimbra@webmail:~/conf/nginx$ grep -n 'listen' templates/nginx.conf.web.https.default.template templates/nginx.conf.web.https.template
templates/nginx.conf.web.https.default.template:5:${web.strict.servername}# The $\{listen.:addresses\} is NOT demarcated with web.strict.servername on purpose.
templates/nginx.conf.web.https.default.template:7:${web.strict.servername} ${core.ipboth.enabled}listen [::]:${web.https.port} default_server ipv6only=off ssl;
templates/nginx.conf.web.https.default.template:8:${web.strict.servername} ${core.ipv4only.enabled}listen ${web.https.port} default_server ssl;
templates/nginx.conf.web.https.default.template:9:${web.strict.servername} ${core.ipv6only.enabled}listen [::]:${web.https.port} default_server ssl;
templates/nginx.conf.web.https.default.template:13:${listen.:addresses}
templates/nginx.conf.web.https.default.template:32: ${core.ipboth.enabled}listen [::]:${web.https.port} ipv6only=off ssl;
templates/nginx.conf.web.https.default.template:33: ${core.ipv4only.enabled}listen ${web.https.port} ssl;
templates/nginx.conf.web.https.default.template:34: ${core.ipv6only.enabled}listen [::]:${web.https.port} ssl;
templates/nginx.conf.web.https.template:7: ${core.ipboth.enabled}listen ${vip}${web.https.port} ipv6only=off ssl;
templates/nginx.conf.web.https.template:8: ${core.ipv4only.enabled}listen ${vip}${web.https.port} ssl;
templates/nginx.conf.web.https.template:9: ${core.ipv6only.enabled}listen ${vip}${web.https.port} ssl;
zimbra@webmail:~/conf/nginx$
4. Restart the proxy service and check that the changes “took”.
zimbra@webmail:~/conf/nginx$ zmproxyctl restart
Stopping proxy...done.
Starting proxy...done.
zimbra@webmail:~/conf/nginx$
zimbra@webmail:~/conf/nginx$ grep -rn 'http2' /opt/zimbra/conf/nginx/includes/
zimbra@webmail:~/conf/nginx$ curl -skI --http2 https://localhost/ -o /dev/null -w '%{http_version}\n'
zimbra@webmail:~/conf/nginx$
A good “outside-looking-in” test is to browse to https://tools.keycdn.com/http2-test and check your proxy server there.
If you need help securing your Zimbra system, just reach out!
Hope that helps,
L. Mark Stone
Mission Critical Email LLC
19 November 2026
The information provided in this blog is intended for informational and educational purposes only. The views expressed herein are those of Mr. Stone personally. The contents of this site are not intended as advice for any purpose and are subject to change without notice. Mission Critical Email makes no warranties of any kind regarding the accuracy or completeness of any information on this site, and we make no representations regarding whether such information is up-to-date or applicable to any particular situation. All copyrights are reserved by Mr. Stone. Any portion of the material on this site may be used for personal or educational purposes provided appropriate attribution is given to Mr. Stone and this blog.
