Rapid7 turns GitLab's CVSS 10.0 regex overflow into command execution on an official 19.4.1 image
Rapid7 built a working command-execution exploit for GitLab's CVSS 10.0 CI/CD regex overflow, CVE-2026-97229. Rapid7 says its route needs a malicious CI config pushed to a public project first, a prerequisite that conflicts with GitLab's PR:N rating.
Reality
- Evidence65
- Adoption
- Not scored
- Hype gap−10
- Incentives
- Not scored
- Confidence60
buildOne report1 publisher GitLab's Dependency Firewall blocks bad packages before a CI job installs them
GitLab put Dependency Firewall into early access with policies for malicious status, severity, license and package age across six package managers. The check is meant to run while the CI job still holds its credentials, according to a dev.to write-up.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap−10
- Incentives
- Not scored
- Confidence55
buildOne report1 publisher Any Duo Agent Platform account can run arbitrary commands on a GitLab AI Gateway server
GitLab has patched CVE-2026-90970, a CVSS 9.9 flaw that lets any authenticated Duo Agent Platform user run arbitrary commands on the AI Gateway server. Fixed releases are 19.2.4, 19.3.2 and 19.4.1 for self-hosted installs.
Reality
- Evidence50
- Adoption
- Not scored
- Hype gap+10
- Incentives
- Not scored
- Confidence45
GitLab patches CVE-2026-97229, an unauthenticated code execution flaw in its CI/CD regex compiler
GitLab patched CVE-2026-97229, an integer overflow in its CI/CD regex compiler that lets unauthenticated users run code on self-managed servers. Separately, Let's Encrypt's 64-day production certificates start February 10, 2027, so renewal automation needs a test run first.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+5
- Incentives
- Not scored
- Confidence65
GitLab patches a CVSS 10.0 code-execution flaw across its 19.2, 19.3 and 19.4 lines
GitLab released critical patches 19.4.2, 19.3.5 and 19.2.8 on October 12 to fix a CVSS 10.0 code-execution flaw. Self-managed installations are told to upgrade immediately, while GitLab.com is already patched and Dedicated customers need do nothing.
Publishers:docs.gitlab.com
Reality
- Evidence68
- Adoption
- Not scored
- Hype gap0
- Incentives
- Not scored
- Confidence72
Bloom Security counted more than 1,500 npm packages exposed because Trusted Publishing bound publish rights to a GitHub repository name. GitHub says it has shipped fixes, and Bloom's Golan Myers said it is unknown whether anyone exploited the flaw.
Perspective Coverage
3 publishers
- Builder
- Builder 45%
- Operator
- Operator 38%
- Investor
- Investor 17%
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+20
- Incentives55
- Confidence64
GitLab fixed CVE-2026-97229, a maximum-severity flaw that could let remote attackers run code, in releases 19.2.8, 19.3.4 and 19.4.2. GitLab.com already runs the fix and Dedicated customers need do nothing, so the work falls on self-managed operators.
Perspective Coverage
7 publishers
- Builder
- Builder 26%
- Operator
- Operator 63%
- Investor
- Investor 11%
Reality
- Evidence85
- Adoption
- Not scored
- Hype gap+10
- Incentives30
- Confidence82
buildOne report1 publisher GitLab's /goal mode lets one model write code while another judges whether the goal is met
GitLab 19.4 adds a /goal command to Duo CLI that loops until a second model judges the objective met or an iteration limit hits. The release adds finer AI spend controls and keeps agent actions inside existing project permissions.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+15
- Incentives60
- Confidence50
buildOne report1 publisher Azure Pipelines' new GitHub-hosted Agents pool prices each job per minute by the image label in its YAML
Microsoft made GitHub-hosted agents generally available in Azure Pipelines, billed per minute at a rate the YAML image label sets, with no free minutes. Anyone with write access to a pipeline can now change what its jobs cost.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap0
- Incentives
- Not scored
- Confidence55
buildOne report1 publisher GitLab patches a second CVSS 9.9 template-sandbox escape in its AI Gateway in eight months
GitLab has fixed CVE-2026-90970, a CVSS 9.9 sandbox escape that lets an authenticated Duo Agent Platform user run commands on self-hosted AI Gateways. Anyone running one of those gateways needs build 19.2.4, 19.3.2 or 19.4.1, all released October 2, to close it.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+12
- Incentives30
- Confidence58
WatchTowr reproduced CVE-2026-19478 from the advisory and patch alone, then caught the first exploitation attempts on its honeypots. Self-managed owners do not get a week to schedule this.
Perspective Coverage
5 publishers
- Builder
- Builder 29%
- Operator
- Operator 63%
- Investor
- Investor 8%
Reality
- Evidence68
- Adoption
- Not scored
- Hype gap+20
- Incentives62
- Confidence70
Azazel, a Russian-speaking affiliate of The Gentlemen RaaS crew, ran his own leak site to extort over two dozen victims and kept the proceeds, CloudSEK found. His way in was secrets left in old GitLab commits.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+15
- Incentives40
- Confidence55
Nike's early layoff warning lets staff with other options leave before the list is drawn
Nike will start deciding which roles to cut in 2027, joining Meta and GitLab in announcing layoffs before naming who is affected. Voluntary exits during the wait may trim severance, though an employment lawyer warns the leavers can include people the company would have kept.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+15
- Incentives55
- Confidence50
buildOne report1 publisher Four MCP servers drew CVEs for exposing every tool without authentication
NVD logged CVEs for four MCP servers in about 35 hours, each because every tool it exposes needs no authentication. A fifth MCP flaw, LiteLLM's authentication bypass, is already on CISA's exploited-vulnerabilities list.
Reality
- Evidence62
- Adoption58
- Hype gap−6
- Incentives45
- Confidence52
buildConfirmed2 publishers OpenAI has fixed a Critical Codex flaw in which a semicolon in a branch name leaked the agent's GitHub OAuth token on all four Codex surfaces. How far one leaked token could reach was set by its scope, which is chosen by whoever provisions the agent.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+10
- Incentives45
- Confidence60
GitLab patched CVE-2026-90970, a sandbox escape that lets any authenticated Duo Agent Platform user run arbitrary commands on a self-hosted AI Gateway. Customers on GitLab's hosted gateway are already protected, so the upgrade falls to Self-Managed shops that run their own.
Perspective Coverage
4 publishers
- Builder
- Builder 24%
- Operator
- Operator 59%
- Investor
- Investor 17%
Reality
- Evidence78
- Adoption
- Not scored
- Hype gap+15
- Incentives
- Not scored
- Confidence74
GitLab's September 10 patch release closes CVE-2026-85706, a CVSS 10.0 path confinement failure in the repository commits API. GitLab.com was already patched, so the exposure sits with self-managed servers.
Perspective Coverage
3 publishers
- Builder
- Builder 33%
- Operator
- Operator 62%
- Investor
- Investor 5%
Reality
- Evidence72
- Adoption
- Not scored
- Hype gap+5
- Incentives30
- Confidence70
buildOne report1 publisher Bitbucket's one-year API tokens schedule a repeat of the app-password outage for July 2027
Bitbucket Cloud's API tokens, which replace app passwords removed on 28 July 2026, expire after one year with no extension, a dev.to migration guide says. Teams that switch in July 2026 have set their next credential failure for July 2027 unless someone owns token rotation.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+10
- Incentives
- Not scored
- Confidence50
OpenAI's Codex now builds a project's environment once and starts each cloud task from it, with task state recoverable for up to seven days. For a team rolling it out, the new job is deciding who may edit the shared setup and what it can reach.
Reality
- Evidence60
- Adoption
- Not scored
- Hype gap+5
- Incentives45
- Confidence65
buildOne report1 publisher Cache lookahead brings a kaniko fork within 1.6x of BuildKit on GitLab runners
Kaniko's community fork, with cross-stage cache lookahead, ran 1.6x slower than BuildKit on GitLab.com runners in a dev.to benchmark. The 15x gap still quoted against kaniko dates from 2018, so teams choosing an in-cluster builder need figures from their own Dockerfiles.
Reality
- Evidence40
- Adoption
- Not scored
- Hype gap+30
- Incentives
- Not scored
- Confidence35