---
title: "GitLab made each AI credit buy up to twice the agent work before its December 1 earnings"
description: "The 19.6 release shipped still carrying a critical, unpatched Ruby flaw. GitLab's fiscal Q3 2027 results, after the US close on December 1, now have to show agent volume outrunning a change that bills less for each task."
publisher: "The Inference"
section: "Platforms"
published: 2026-11-20T16:07:44.309Z
modified: 2026-11-20T16:07:44.309Z
canonical: https://theinference.org/article/gitlab-made-each-ai-credit-buy-up-to-twice-the-agent-work-before-its-december-1-earnings
language: en
keywords: "GitLab, Earnings, Agentic AI, Cybersecurity, Developer Tools"
---

# GitLab made each AI credit buy up to twice the agent work before its December 1 earnings

> The 19.6 release shipped still carrying a critical, unpatched Ruby flaw. GitLab's fiscal Q3 2027 results, after the US close on December 1, now have to show agent volume outrunning a change that bills less for each task.

[GitLab](https://theinference.org/markets/companies/gitlab) (NASDAQ: GTLB) shipped 19.6 on November 19, 2026, as its agent-security showcase: Duo agents that fix vulnerabilities across whole groups, automations that run unattended, and MCP, the protocol agents use to call tools, governed tool by tool as Always Allow, Ask or Deny [1]. The same release made each GitLab Credit, the meter that bills agentic work, buy up to twice as much agent labor on the Duo Agent Platform, at once for new customers and from December 18 for the rest [1].

Within hours of shipping, users pulling 19.6.0 from the package repositories found it still carried a flaw in Ruby, disclosed the night before [2]. Together the two moves set the question GitLab's fiscal Q3 2027 results, due after the US close on December 1, must answer: does agent volume grow faster than billing per task shrinks [3]?

## The showcase shipped on a flawed runtime

The flaw is Ruby2Shell, [a heap overflow in Ruby's string case conversion](https://render.com/docs/advisory-ruby2shell), among seven flaws Ruby patched on November 18 [4]. The Ruby security team rates it critical and says it may allow remote code execution; in GitLab, case-changing a crafted string can write out of bounds [5].

Every self-managed instance, the copy a customer runs on its own servers, was exposed until the patch [5].

## An older web server stayed bundled even after the Ruby fix

Even the patched release still bundles an NGINX, the web server inside GitLab's package, older than the November 18 upstream fixes; turning HTTP/2 off closes the two most exposed of those flaws, while Ruby2Shell has no workaround [2][6].

GitLab answered inside a day: [a critical patch release on November 20](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/) moved the bundled Ruby to the fixed 3.3.14, and GitLab.com was already remediated [5]. That capped a week that began with gitlab.com serving malware through a hacked script from Optimizely, a vendor whose web-personalization code runs on other companies' sites [7]; we covered that week's 37-flaw patch day [in full](https://theinference.org/article/gitlab-patched-37-flaws-ten-in-its-ai-agent-tools-the-same-day-gitlab-com-carried-a-hacked-optimizely-script).

## Each agent task now bills fewer credits

Credits are what customers buy; agent tasks are what spends them. Each task now issues fewer model requests, so most customers' credits stretch up to twice as far, and GitLab is steering the freed credits into the new security flows, automations and Slack agents [1].

A unit of agent work just got up to half as expensive to bill. GitLab is betting it sells the volume back.

*Chart: **Yearly revenue growth has cooled from 31% to 21% in two years** Line chart of GitLab year-over-year revenue growth across eight quarters, falling from 31% in Q3 2024 to 21.3% in Q2 2026*

*Year-over-year revenue growth in percent, calendar quarters, from GitLab's SEC filings [9]*

The October quarter closed on the 31st, before any of this, so [the December 1 report](https://finance.yahoo.com/markets/stocks/articles/gitlab-announce-third-quarter-fiscal-210500535.html) is the last clean baseline [3]. The deflation binds in the December quarter, and shows up first in guidance [3].

## Security buyers' trust now gates the agent rollout

The chain is short: agents fix findings, backlogs clear, security staff stop being the queue. The first hop ships now, mostly in beta [1][8].

The permission to run it is granted by the same security teams that spent the week watching their vendor patch a critical flaw in its own runtime a day after release [5], days after a hacked third-party script served malware off gitlab.com [7]. A one-day patch with a public advisory is the strongest signal GitLab could send that its agent controls are real [5].

Cheaper agent labor is how backlogs actually clear, so the credit cut is the right call. On December 1, read agent volume; in December-quarter guidance, read whether volume absorbs the deflation [3].

*Chart: **Revenue is up 46% since late 2024 while the operating loss widened to $57M** Column chart of GitLab quarterly revenue and GAAP operating income across eight quarters: revenue rises from $196M to $286M while operating income stays negative and the loss widens to $57M in Q2 2026*

*Quarterly revenue and GAAP operating income in millions, calendar quarters, from GitLab's SEC filings. The October quarter reported on December 1 predates the credit change. [9]*

## Takeaway

GitLab halved what each credit buys in agent work, so the December 1 report has to show customers spending the freed credits on more agents, not simply paying less for the same work.

## Sources

1. [Business Wire via Yahoo Finance, 'New GitLab Agentic Automations Clear the Security Backlog and Do Up to Twice the Work For The Same Cost', 19 November 2026](https://finance.yahoo.com/technology/ai/articles/gitlab-agentic-automations-clear-security-213000673.html)
2. [Hacker News, 'GitLab 19.6.0 is out and still vulnerable to Ruby2Shell and NGINX2Root', full thread record via Algolia API, 19-20 November 2026](http://hn.algolia.com/api/v1/items/50561571)
3. [Business Wire via Yahoo Finance, 'GitLab To Announce Third Quarter Fiscal 2027 Financial Results', 17 November 2026](https://finance.yahoo.com/markets/stocks/articles/gitlab-announce-third-quarter-fiscal-210500535.html)
4. [Render, 'Advisory: Ruby2Shell and Associated Vulnerabilities', 19 November 2026](https://render.com/docs/advisory-ruby2shell)
5. [GitLab Docs, 'GitLab Critical Patch Release: 19.6.1, 19.5.8, 19.4.10', 20 November 2026](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/)
6. [AlmaLinux OS Blog, 'NGINX2Root: Patched nginx packages released', 18 November 2026](https://almalinux.org/blog/2026-11-18-nginx2root/)
7. [BleepingComputer, 'Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware', 16 November 2026](https://www.bleepingcomputer.com/news/security/optimizely-supply-chain-attack-delivers-malware-to-cnn-fox-news-bbc-salesforce-sites/)
8. [GitLab Docs, 'GitLab 19.6 release notes', 19 November 2026](https://docs.gitlab.com/releases/19/gitlab-19-6-released/)
9. [GitLab, quarterly figures from its SEC filings, retrieved 20 November 2026](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001653482)


---

GitLab made each AI credit buy up to twice the agent work before its December 1 earnings — The Inference. Canonical: https://theinference.org/article/gitlab-made-each-ai-credit-buy-up-to-twice-the-agent-work-before-its-december-1-earnings
