Repository navigation
chore(release): prepare v4.14.1 - #1967
Conversation
Move easyengine/nginx-proxy to v4.14.1, which updates its nginx from 1.31.3 to 1.31.9 for the nginx security fixes of 2026-11-18 (CVE-2026-123633, CVE-2026-123007, CVE-2026-118899, CVE-2026-123634) and the earlier 1.31.6 and 1.31.7 fixes (EasyEngine/dockerfiles#379). The other images are unchanged.
|
No actionable comments were generated in the recent review. Walkthrough
Change: Other Merge Risk:
|
Summary
v4.14.1: a security release for the nginx vulnerabilities fixed in nginx 1.31.9 on 2026-11-18, among them the HTTP/2 vulnerabilities CVE-2026-123633 and CVE-2026-123007, the TLS 1.3 request-body loop CVE-2026-118899 and the resolver use-after-free CVE-2026-123634 (nginx security advisories).VERSIONfrom4.14.0to4.14.1.img-versions.json):easyengine/nginx-proxymoves tov4.14.1, whose nginx goes from 1.31.3 to 1.31.9 (with the 1.31.6 and 1.31.7 fixes too) (fix(nginx-proxy): update nginx to 1.31.9 for the 1.31.7 and 2026-11-18 security fixes dockerfiles#379; tagv4.14.1). No other image changes; the otherv4.14.1image tags are unchanged rebuilds and aren't used.composer.jsonandcomposer.lockare untouched.Refs #1966
Upgrade notes
ee cli updatepulls the new nginx-proxy image and recreates only the global proxy. Sites are unreachable for the few seconds the proxy takes to restart; site containers aren't touched.nginx -tfirst and stops without changing anything if it fails. If the new proxy doesn't come up, the previous one is restored.Testing
easyengine/nginx-proxy:v4.14.1as published:nginx -vis 1.31.9,nginx -tpasses with our config and with all dynamic modules loaded, docker-gen renders the template for a test site, and over HTTPS ALPN negotiatesh2and both HTTP/2 and HTTP/1.1 requests are proxied to the backend.EasyEngine v4.14.1; the sites return the same responses before and after, including HTTP/2 over HTTPS; no new migration rows. Sites were unreachable for about 1 s or less while the proxy was swapped (0.3 s on a GitHub runner, 0.5–1.1 s on a test server). As on every update, the global cron container is restarted when its config is regenerated.