Update NGINX from 1.31.4 to 1.31.7
What does this MR do?
Updates the bundled NGINX from 1.31.4 to 1.31.7 (config/software/nginx.rb).
NGINX 1.31.7 (released October 14th) fixes several security issues:
- CVE-2026-15176: buffer overflow when using
aliaswithrewrite - CVE-2026-93479: buffer overflow in script evaluation
- CVE-2026-95101: request body injection in HTTP/3
- CVE-2026-97629: session forgery when using TLS session tickets
- CVE-2026-97205: use-after-free when using asynchronous file I/O (AIO)
As noted in the issue, CVE-2026-97629 is the one most relevant to Omnibus. Our bundled config sets ssl_session_tickets off by default (nginx_helper.rb), but users can turn it on through gitlab.rb. We don't build HTTP/3, so CVE-2026-95101 doesn't apply.
Notes for reviewers
- UBT: the UBT line (
#{display_version}-2ubtand its sha256) is unchanged. I couldn't reach thegitlab-toolchainpackage registry without credentials to confirm that a1.31.7UBT artifact exists or to compute its checksum. A Build team member needs to confirm or provide it beforeTrigger:ee-package-ubtcan pass. Previous bumps (1.29.4, 1.29.8) updated it in a follow-up commit. - Newer patch:
release-1.31.8is also available upstream and on the omnibus-mirror. This MR targets1.31.7as requested in the issue. We may want to go straight to 1.31.8 instead. - There are no
config/patches/nginxpatches to rebase. nginx isn't inconfig/software_versions.ymlyet, so the version still lives in the software definition.
Local test plan
release-1.31.7exists both upstream and ongitlab-org/build/omnibus-mirror/nginx, at the same commit (28c4fc45).src/core/nginx.hreports1.31.7.ruby -candrubocoppass onconfig/software/nginx.rb.- Loading the definition with
Omnibus::Software.loadresolvesdefault_version=release-1.31.7anddisplay_version=1.31.7. - Compiled 1.31.7 locally (macOS, clang, OpenSSL 3) with our configure flags plus
nginx-module-vts(v0.2.6) andngx_security_headers(0.0.9). It built with 0 warnings. - Runtime smoke test of that binary:
hide_server_tokensremoves theServerheader, the security headers are set, and the VTS Prometheus endpoint reportsversion="1.31.7"(the checks from #8437 (closed)).
These still need CI: build-package-on-all-os, Trigger:package:fips (this touches SSL), the UBT pipeline, and QA.
Related issues
Closes #10147 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
- MR title and description are up to date, accurate, and descriptive.
- MR targeting the appropriate branch.
- Latest Merge Result pipeline is green.
- When ready for review, MR is marked as ready (not a draft) and a reviewer is requested. Pick the reviewer suggested by the reviewer roulette, or one of the project maintainers.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
- The manual
Trigger:ee-packagejobs have a green pipeline running against latest commit.- To debug QA failures, refer to the Investigate QA failures section.
- If
config/softwareorconfig/patchesdirectories are changed, make sure thebuild-package-on-all-osjob within theTrigger:ee-packagedownstream pipeline succeeded. - If you are changing anything SSL related, then the
Trigger:package:fipsmanual job within theTrigger:ee-packagedownstream pipeline must succeed. - If CI configuration is changed, the branch must be pushed to
dev.gitlab.orgto confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
- Test plan indicating conditions for success has been posted and passes.
- Documentation created/updated.
- Tests added.
- Integration tests added to GitLab QA.
- Equivalent MR/issue for the GitLab Chart opened.
- Validate potential values for new configuration settings. Formats such as integer
10, duration10s, URIscheme://user:passwd@host:portmay require quotation or other special handling when rendered in a template and written to a configuration file.
Reviewer checklist
- As soon as you begin reviewing, select Start a review on your first comment so the MR shows Reviewer started review.