SECOND MEASUREMENT SM-027

GitLab says the issue behind every security fix goes public 90 days after the fix ships. Of the 176 fixed from January to mid-August 2026, 153 are still hidden

Markovian ProtocolMeasured 2026-10-28 and 2026-11-13Status: published 2026-11-16; advance copy sent 28 October 2026DOI: 10.5281/zenodo.24237272

The claim: GitLab security issues: the disclosure page says every issue goes public 90 days after the fix; of 176 fixed January to July 2026, 153 are still hidden

What we found: 153 of 176 issues for vulnerabilities fixed January to July 2026 still hidden from logged-out visitors (86.9%). Earlier years: see the page.

Status: Published 16 Nov; checked against the exhibits before publication; advance copy sent to GitLab's security team 28 Oct as a confidential issue

GitLab fixes security vulnerabilities in its patch releases. While a fix is being made, the issue that describes the vulnerability is confidential; afterwards GitLab promises to open it to everyone. Once open, anyone who runs a GitLab server, or tracks its vulnerabilities, can read what was wrong. Its disclosure page says: “All vulnerabilities will be made public via our issue tracker 90 days after releasing the fix.” From 7 January to 24 June 2026 each security patch release said 30 days. We took every issue that GitLab’s own vulnerability records (CVEs) cite and asked GitLab.com, logged out, whether it could be seen. On 13 November 2026, 153 of the 176 issues for vulnerabilities fixed between January and 12 August 2026, all more than 90 days earlier, could not be seen (86.9%). Every one fixed from May on was hidden, and none had been opened since our first read on 28 October. For fixes from 2020 to 2024 the share hidden on the same day is between 10.8% and 31.6%; for 2025 fixes, 43.5%.

The short version

Disclosure: Markovian Protocol holds no financial position in GitLab or any competitor, was paid by no one for this work, and uses GitLab.com only to read public pages. We sent a copy to GitLab’s security team on 28 October, as a confidential issue on GitLab.com, 19 days before publication; nobody else saw it. How we work.

The promise, in their words

WhereDateWhat it says
Security patch release notes, 12 releases7 Jan to 24 Jun 2026“For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.”
Security patch release notes, 10 releases8 Jul to 21 Oct 2026The same sentence, with 90 days.
Security release notes29 Oct and 10 Nov 2026No such sentence. The 29 October security update uses a shorter layout without the usual introduction; the 10 November critical release has the usual introduction without that sentence.
Security disclosure pageread 28 Oct and 13 Nov 2026“All vulnerabilities will be made public via our issue tracker 90 days after releasing the fix. We try and redact all information considered sensitive (such as cookies, tokens, data details). The only time we will make an exception and not make a vulnerability public is when it contains sensitive data which we are unable to redact or remove from the report.”
Handbook, Engaging with Securityread 28 Oct and 13 Nov 2026“we publicly disclose all security vulnerabilities 90 days after a patch is released”; the GitLab Security Bot “comments on confidential issues 90 days after issue closure when they are not labeled ~keep confidential”

We saved every 2026 patch release note we could find on docs.gitlab.com, 31 notes, in sm-027/exhibits/patch_notes_2026/. The 22 security releases from 7 January to 21 October, scheduled and critical alike, each state a delay: 30 days in every one through 24 June and 90 days in every one from 8 July. The two security releases since do not: the 29 October security update (19.5.3) uses a shorter layout with no such paragraph, and the 10 November critical release (19.5.4) has the usual opening paragraph without the sentence. The other seven notes, six bug-fix releases and one undated note, say nothing about it. The disclosure page and the handbook still say 90 days on 13 November; both reads are saved beside them.

Year by year

Fixed inIssues more than 90 days oldHiddenShare
2020 (from June)1042322.1%
20211524831.6%
20221434430.8%
20231661810.8%
20241453524.1%
20251687343.5%
2026 (January to 12 August)17615386.9%

“Fixed in” is the date the CVE was published, as recorded by the National Vulnerability Database; an issue cited by two CVEs is dated by the older one. Of the 254 issues from 2026, 219 have a CVE published on a patch release day or the day after, and the other 35 between 2 and 14 days after the nearest earlier release, so using the CVE date can only make an issue look younger than it is. An issue counts once it was more than 90 days old when we asked for it; the last CVE counted was published on 12 August at 20:17 UTC, 92 days and 22 hours before our first request on 13 November. Leaving out that release gives 140 of 163 (85.9%); the releases that promised 30 days alone give 120 of 143 (83.9%).

2026, month by month

Fixed inIssuesHidden on 13 NovemberPromise in the release notes
January13830 days
February251330 days
March272230 days
April232230 days
May313130 days
June242430 days
July (8 and 29 July releases)202090 days
August (12 August release)131390 days

Of the 120 hidden issues from releases that promised 30 days, the youngest came from the 24 June release, 142 days before 13 November.

How we know an issue is hidden

A public issue answers 200 to an anonymous request for https://gitlab.com/api/v4/projects/278964/issues/<number>; a confidential or missing one answers 404. We made that request for all 1,132 issues from two places on 13 November: a home connection in Colorado and a server in Helsinki. The answers matched for every issue. (On 28 October, when we first ran it for 1,131 issues, one, 595468, answered 404 from Colorado and got no response from Helsinki; it is counted as hidden in the 28 October figures.) Three further checks:

A 404 cannot tell a confidential issue from a deleted one. GitLab’s CVE records still cite these issues as references for each vulnerability, so we treat them as confidential.

When issues did go public

For public issues, GitLab records a system note, “made the issue visible to everyone”, when the issue is opened (an example is saved for issue 587698). From the CVE date to that note: 2025 fixes, median 40.5 days (88 issues read); 2026 fixes, median 70 days (17 issues). In 6 of these 105 the issue went public before its CVE was published; for those the CVE date understates the time from the fix. Where GitLab’s API limited our requests on 13 November we used the 28 October read of the same issue (42 issues); missing from these medians: 12 public 2025 and 2026 issues still unread, one public issue with no such note, and one dated 2024 by its older CVE.

How this ends

GitLab can end this in two ways, both within its own control: open the issues the policy says should be public, or say how many 2026 issues are held back and why. Our monthly recheck repeats the anonymous probe on the first of each month and will show the first. The second is a reply, which we will print in full.

Probe2026 issues more than 90 days oldHiddenShareOpened since the previous probe
28 Oct 202616314085.9%–
13 Nov 202617615386.9%0
16 Nov 202617815587.1%0

From the 1st of each month the probe runs from the Helsinki server alone, with the same counting rules; each run adds a row and the page is stamped again. Script: sm-027/recheck/recheck.py.

Our questions

  1. How many security issues for vulnerabilities fixed in 2026 carry the “keep confidential” label, and how many are held back because they contain sensitive data that cannot be redacted?
  2. Has the step that makes fixed security issues public been paused since the spring of 2026, and if so, when will the backlog be published?
  3. For issues fixed in releases whose notes promised 30 days, does GitLab now apply 90?

We sent these to GitLab’s security team with the advance copy on 28 October and will print the answers as written.

What we can’t be sure of

Run it yourself

D=$(date -u +%F); mkdir -p data exhibits
curl -s 'https://services.nvd.nist.gov/rest/json/cves/2.0?sourceIdentifier=cve@gitlab.com'   # one page holds 2,000; page with &startIndex= beyond that > "exhibits/nvd_cves_source_cve@gitlab.com_$D.json"
python3 -I extract.py "exhibits/nvd_cves_source_cve@gitlab.com_$D.json" > data/cve_issue.csv
bash probe.sh && mv data/probe_$(date -u +%Y%m%d).csv "exhibits/probe_mac_$D.csv"
#   run probe.sh again from a second network and save it as exhibits/probe_hetzner_$D.csv
python3 -I apicheck_lag.py "exhibits/probe_hetzner_$D.csv" out    # GraphQL check and visibility notes; slow, GitLab rate-limits anonymous queries
mv out_apicheck.csv "exhibits/graphql_workitem_check_$D.csv"; mv out_lag.csv "exhibits/visibility_lag_$D.csv"
python3 -I analyze.py                                             # uses the newest dated file of each kind; writes summary.json, rows.csv
python3 -I handcheck.py "exhibits/probe_mac_$D.csv" "exhibits/cveorg_$D/"   # the 30-issue cve.org check

Standard-library Python 3 and curl. analyze.py takes the probe date from the file name, so a later run gives that day’s counts, not ours. Scripts and exhibits: sm-027/. Where and when each file was made: exhibits/README.txt.

References

  1. GitLab, Security disclosure, about.gitlab.com/security/disclosure, read 28 October and 13 November 2026. Saved copies gitlab_security_disclosure_2026-10-28.html, gitlab_security_disclosure_2026-11-13.html.
  2. GitLab patch release notes, 7 January to 12 November 2026, docs.gitlab.com/releases/patches. Saved copies in sm-027/exhibits/patch_notes_2026/.
  3. GitLab Handbook, Engaging with Security, handbook.gitlab.com, read 28 October and 13 November 2026. Saved copies handbook_engaging_with_security_2026-10-28.html, handbook_engaging_with_security_2026-11-13.html.
  4. NIST National Vulnerability Database, CVE API 2.0, sourceIdentifier=cve@gitlab.com, read 28 October and 13 November 2026; and the CVE Program’s records at cveawg.mitre.org/api/cve/<id>.
  5. GitLab REST API /api/v4/projects/278964/issues/<iid> and GraphQL API gitlab.com/api/graphql, requested without a login on 28 October and 13 November 2026.