DE — heise online
GitLab 19.6 Adds Audit Log for AI Agents, NGINX Remains Vulnerable
Software2 min read
GitLab released version 19.6 of its DevSecOps platform, adding audit logs that track what AI agents do. The launch is overshadowed by security holes in Ruby and NGINX that GitLab ships with its software.
New AI agent audit logs
GitLab 19.6 records what AI agents do through GitLab's own MCP server. MCP (Model Context Protocol) is a way for AI tools to talk to other software. Every agent action creates an audit event. You can find these events under AI > Governance at the top-level group. Free users get the audit feature. Premium and Ultimate customers also get governance for MCP server tools. Server-side enforcement is still in beta and needs two feature flags, which are off by default.
Key facts
- Audit logging is available to all tiers, including Free.
- Owners can set each MCP tool to Always Allow, Always Ask, or Always Deny. This has been possible since version 19.4.
- Blocked tools are now hidden from agents before they see them, once server-side enforcement is on.
- Version 19.6.1 was released on 20 November with 19.5.8 and 19.4.10. It fixes the bundled Ruby.
Other new features
GitLab Duo Agentic Chat used to answer one message and then wait. Now the /goal command starts a long task. It runs a Developer Flow session until the task is done. Also, Duo flows in the runner used to keep running without isolation when no sandbox was available, with only a warning. A new option makes the job fail in that case.
Why it matters
Companies that use AI agents need to know what those agents do. The new logs and server-side blocks give admins more control. But the Ruby and NGINX holes mean self-hosted GitLab users must patch quickly, or take manual steps to reduce risk.
What to watch
- Self-hosted users should install GitLab 19.6.1 to fix Ruby (CVE-2026-132825, rated critical).
- NGINX in GitLab 19.6 is still version 1.31.7, which is vulnerable to five nginx2root flaws. The fixes are in NGINX 1.30.7 and 1.31.9.
- Admins can turn off HTTP/2 with nginx['http2_enabled'] = false and run gitlab-ctl reconfigure. This removes two of the five flaws.
- Check custom NGINX settings before upgrading. Zero buffer sizes now fail, and IP certificate checks need IP entries.
- In runner 19.6, jobs with FF_CONCRETE use the configured shell. If it is sh, Bash arrays may fail.
Glossary
- GitLab
- A company and platform that helps software teams write, test, and ship code.
- MCP
- Model Context Protocol, a way for AI tools to connect to other software.
- NGINX
- Popular web server software that sends web pages and handles web traffic.
- Ruby
- A programming language. GitLab bundles it to run parts of its system.
- HTTP/2
- A newer version of the web's main communication protocol, which makes pages load faster.