On 24 September 2026, GitHub Security Lab released an autonomous fuzzing pipeline that writes its own harnesses, reads its own coverage and drafts its own vulnerability reports. The fuzzing bottleneck — human attention — is handed to an LLM, but the code runs on the host with no container in between.
Released September 17, 2026, GitLab 19.4 governs MCP server tools, restricts their access, and hands agents pipeline control through save_pipeline and get_job. For teams deploying AI agents in the enterprise, the DevSecOps control plane becomes the governance layer.
On September 11, 2026, GitLab shipped an out-of-band release for CVE-2026-85706, a CVSS 10 path traversal that reads server files with no authentication via the commits API. The flaw is already being probed in the wild — patch self-managed instances before an attacker reads secrets.yml.
On August 18, 2026, GitLab released fixes for two vulnerabilities, including a critical code injection via a GraphQL directive (CVE-2026-19478, CVSS 9.4) exploitable remotely without authentication or user interaction, allowing attackers to modify or delete public projects. Every self-managed installation must upgrade immediately — GitLab.com and GitLab Dedicated are already patched.
Chrome 149 and 150 shipped 1,072 security fixes discovered, triaged, and patched by AI agents. Google automated the entire vulnerability management chain — fuzzing, reproduction, triage, patching — and it changes everything about how your DevSecOps pipeline should work.
On March 17, 2026, GitHub Enterprise Server 3.20 went GA with two structural security gates: releases are now immutable by default, and secret scanning gains enterprise-wide governance controls. Against a backdrop of escalating supply chain attacks, this release turns the forge into a fortress.
GitLab 19.0 shipped on May 21, 2026 with a native Secrets Manager, AI-driven merge requests, and an SBOM scanner. The platform closes the gap between writing code and shipping it securely — a gap GitHub Copilot still leaves open.
