Double Free in GitLab
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 19.2.7, 19.3.3, 19.4.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
GitLab Community Edition and Enterprise Edition are affected. Under certain conditions, an authenticated user could exploit a memory handling flaw triggered by a specially crafted regular expression in a CI/CD configuration to run arbitrary code on the GitLab server.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- GitLab GitLab
From 19.2 · fixed in 19.2.7; From 19.3 · fixed in 19.3.3; From 19.4 · fixed in 19.4.1
- gitlabBitnami
From 19.2.0 · fixed in 19.2.7; From 19.3.0 · fixed in 19.3.3; From 19.4.0 · fixed in 19.4.1
References 3
gitlab.com
hackerone.com
docs.gitlab.com
Questions about CVE-2026-89078
What does this mean?
A double free is a memory bug where the same memory block is released twice. Here it is triggered by parsing a specially crafted regular expression in a CI/CD configuration, and it could let an authenticated user execute arbitrary code on the GitLab server.Source: docs.gitlab.com
Am I affected, and how do I check?
GitLab CE and EE versions from 19.2 before 19.2.7, from 19.3 before 19.3.3, and from 19.4 before 19.4.1 are affected. To check a GitLab instance, look at its version in the Admin area or by running the version check on the server, then compare it with those ranges.Source: docs.gitlab.com
What should I do about it?
Upgrade to GitLab 19.2.7, 19.3.3, or 19.4.1, matching your release line. No workaround is listed in the facts.Source: docs.gitlab.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data