nday
CVE-2026-89078

Double Free in GitLab

GitLab / GitLab

Technical analysis appeared 30 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typedouble free accessnetworkno user interaction productGitLab product typedeveloper / CI tooling
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

double free
CWE-415, stated by the CNA GitLab and NVD, republishing [email protected]
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L (CVSS 3.1) from the CNA GitLab
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L (CVSS 3.1) from the CNA GitLab
GitLab
affected products in the CVE record: GitLab · GitLabCPE names NVD's analysts give as vulnerable: a:gitlab:gitlab
developer / CI tooling
affected products in the CVE record: GitLab · GitLabCPE names NVD's analysts give as vulnerable: a:gitlab:gitlabthe product type of GitLab in nday's product registry
stage
ANA
disclosed
cvss
9.9 CRITICAL v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-23T23:05Z
PATpatch
no record yet
ANAanalysis
10-23T18:10Z
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to a double free issue when parsing a specially crafted regular expression in a CI/CD configuration.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

CVSS 3.1 vector from the CVE record, scored by the CNA GitLab.

Event log

+DISdisclosed

CVE record published by GitLab. CVSS 9.9, critical.

src cvelist · nday , bulk import · raw
{
  "id": 451926,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-89078",
  "occurred_at": "2026-09-23T23:05:20.132Z",
  "observed_at": "2026-11-13T05:40:14.931471Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L",
      "version": "3.1",
      "base_score": 9.9,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2026-09-24T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-09-23T23:05:20.132Z",
    "assigner_short_name": "GitLab"
  }
}
+ANAtechnical analysis

Posted to the oss-security mailing list: “Ruby Regexp compilation fixes related to GitLab's CVE's”.

src osssec 2026/q4/360 · nday , observed live · raw
{
  "id": 495872,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/360",
  "occurred_at": "2026-10-23T18:10:34Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/360",
  "detail": {
    "list": "oss-security",
    "author": "Alan Coopersmith",
    "subject": "Ruby Regexp compilation fixes related to GitLab's CVE's",
    "is_reply": false
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.