GitLab 19.6 Ships Agent Audit Logs; Bundled NGINX Still Exposed to Five nginx2root Flaws
Article Content
- •Self-managed GitLab users should upgrade to 19.6.1 to fix CVE-2026-132825 (Ruby2Shell), which Ruby rates critical.
- •GitLab 19.6 still bundles a vulnerable NGINX 1.31.7; CVE-2026-123007 (CVSS 8.1) is exploitable without authentication via HTTP/2.
- •Heise advises disabling HTTP/2 via nginx['http2_enabled'] = false as an interim mitigation until GitLab ships a fixed NGINX.
- •GitLab 19.6 adds audit events for all MCP server agent actions, viewable under AI > Governance, available on all tiers.
- •Exploitation in the wild is not reported in these articles.
GitLab released version 19.6 of its DevSecOps platform, adding audit events for every AI agent action taken through the GitLab MCP server, available across all tiers including Free. Heise reports that the release is overshadowed by two security issues affecting self-managed installations. The first is CVE-2026-132825 (Ruby2Shell), a heap buffer overflow in Ruby case conversion that the Ruby team rates and considers capable of remote code execution in some scenarios; it was fixed in GitLab 19.6.1, released 2026-11-20 alongside versions 19.5.8 and 19.4.10. Heise states that Linux packages, container images and GitLab.com have been patched, while source installs must rebuild Ruby 3.3.14 or 3.4.13. The second issue is five nginx2root vulnerabilities disclosed 2026-11-18 that affect the NGINX version GitLab 19.6 bundles (1.31.7). The most severe, CVE-2026-123007 (CVSS 8.1), sits in the HTTP/2 code and can be exploited without authentication. Heise says the patches do not update the bundled NGINX, which is only fixed in NGINX 1.30.7 and 1.31.9, and that HTTP/2 is enabled by default in the Linux package and Docker image. Until GitLab ships an update, Heise advises setting nginx['http2_enabled'] = false in gitlab.rb and running gitlab-ctl reconfigure, which mitigates two of the five flaws; the other three affect HTTP/3, the DNS resolver and the mail proxy. The articles do not report exploitation in the wild, and the cluster's sources are a Heise news article and GitLab's own release notes.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Common questions
Am I affected if I run self-managed GitLab?
How urgent is the NGINX problem?
What should admins do before a fixed NGINX ships?
Continue Reading
Lazarus Group Targets 30 South Korean Servers Using PHP Vulnerabilities North Korea-linked Lazarus Group has targeted 30 servers in South Korea as part of a larger cyber operation involving 581 servers across 10 countries. The attacks exploit two critical remote code execution vulnerabilities in PHP (CVE-2026-109618 and CVE-2026-109619), allowing unauthorized server command execution. The…