Applies to: Mattermost Server 11.x (verified on v11.7.15) deployed behind an nginx reverse proxy or ingress-nginx running nginx 1.31.8 or earlier.
Status: No Mattermost update required; fixed in nginx 1.31.9 and 1.30.7 (as of 2026-11-19).
Context: Guidance for administrators and security teams assessing the nginx security advisories published on November 18, 2026.
đź‘“ Overview
Mattermost Server is not affected: the Mattermost package and Docker image do not include nginx. The vulnerabilities, including the major HTTP/2 flaw CVE-2026-123007, are in nginx itself, which you run as a separate reverse proxy in front of Mattermost. The fix is to upgrade nginx to 1.31.9 (mainline) or 1.30.7 (stable). Disabling HTTP/2 mitigates the two HTTP/2 vulnerabilities only; CVE-2026-118899 (TLS 1.3 request body) and the other fixes in that release still require the upgrade.
đź’ˇ Recommendation
Upgrade nginx to a fixed version. If you cannot upgrade immediately, disable HTTP/2 as a partial interim mitigation. Mattermost itself needs no change or restart.
Upgrade nginx
Upgrade to nginx 1.31.9 or 1.30.7, or to your Linux distribution's nginx package that includes these fixes. Reload nginx after the upgrade.
-
Mattermost Docker deployment: the nginx container uses the floating
nginx:alpineimage tag. Pull the updated image once it carries the fixed version, then recreate the nginx container. If you setNGINX_IMAGE_TAGin.envto a fixed version, change it to a fixed release. - Kubernetes with ingress-nginx: upgrade to an ingress-nginx controller release built on a fixed nginx version.
Disable HTTP/2 Until You Upgrade
Mattermost works normally over HTTP/1.1, including WebSocket connections.
Remove http2 from every listen line on port 443, both IPv4 and IPv6, in every server block that uses that port. The Mattermost NGINX configuration guide uses listen 443 ssl http2;, and that parameter keeps HTTP/2 enabled even when http2 off; is set.
listen 443 ssl; listen [::]:443 ssl; http2 off;
On nginx 1.25.1 or later, remove any http2 on; line and add http2 off; as shown. On versions before 1.25.1, nginx does not recognise the http2 directive: remove http2 from the listen lines only.
⚠️ Important: HTTP/2 is enabled for a port if any
serverblock on that address and port hashttp2on itslistenline. One missedserverblock keeps HTTP/2 on for all of them.
Test the configuration and reload nginx:
nginx -t && systemctl reload nginx
To revert, add http2 back to the listen lines (or set http2 on;) and reload nginx.
⚠️ Important: Disabling HTTP/2 does not address CVE-2026-118899, which affects TLS 1.3 connections, or the fixes for the resolver, HTTP/3, mail and stream modules. Only upgrading nginx closes those.
Verify the Result
Check the running nginx version:
nginx -v
The version must be 1.31.9 or later, or 1.30.7 or a later 1.30.x release. If you applied the interim mitigation, confirm HTTP/2 is no longer offered; the command prints HTTP/1.1:
curl -sI --http2 https://<your-mattermost-host>/ | head -1
Comments
Article is closed for comments.