Skip to content
GitLab 19.6 Ships Agent Audit Logs; Bundled NGINX Still Exposed to Five nginx2root Flaws

GitLab 19.6 Ships Agent Audit Logs; Bundled NGINX Still Exposed to Five nginx2root Flaws

First seen 20 Nov 2026, 20:47 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 20, 2026 at 20:48 UTC
  • •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.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-11-18
nginx2root NGINX vulnerabilities disclosed
Five NGINX flaws disclosed, including CVE-2026-123007 in HTTP/2 code; fixed only in NGINX 1.30.7 and 1.31.9.
Heise.De
2026-11-18
CVE-2026-123007 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-11-19
CVE-2026-132825 (Ruby2Shell) published
Heap buffer overflow in Ruby case conversion; the Ruby team rates it critical and considers RCE possible in some scenarios.
Heise.De
2026-11-20
GitLab 19.6 and 19.6.1 released
GitLab 19.6 added MCP audit events; 19.6.1, released alongside 19.5.8 and 19.4.10, replaces the bundled Ruby to fix CVE-2026-132825.
Heise.De
2026-11-20
First public PoC for CVE-2026-132825
Known public proof-of-concept date for the Ruby2Shell vulnerability.

More articles in this cluster (2)

Common questions

Am I affected if I run self-managed GitLab?
Heise reports that any self-managed GitLab running an earlier Ruby build is affected by CVE-2026-132825, and that GitLab 19.6's bundled NGINX 1.31.7 is affected by the nginx2root flaws. Heise and GitLab both direct self-managed users to update to 19.6.1.
How urgent is the NGINX problem?
Heise rates CVE-2026-123007 as the most dangerous of the five nginx2root flaws because it can be exploited without authentication over HTTP/2, which is enabled by default in the Linux package and Docker image.
What should admins do before a fixed NGINX ships?
Heise advises setting nginx['http2_enabled'] = false in gitlab.rb and running gitlab-ctl reconfigure, which mitigates two of the five flaws; the others affect HTTP/3, the DNS resolver and the mail proxy, and custom NGINX directives should be reviewed.