major vulnerability· requires attention

GitLab is a widely used DevOps platform; an RCE in CI can compromise repos, pipelines, runners and many organizations.

Applications

CVE-2026-89078

9.9

Critical

EPSS 0.52%Patch available

Authenticated RCE in GitLab CI via crafted regex (double-free).

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

EPSS 0.52%top 56% of scored CVEs

Published 23 Sept 2026Analysed here 24 Sept 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-89078 being exploited?

Not confirmed. CVE-2026-89078 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-89078?

CVE-2026-89078 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-89078?

Yes. A fix has been recorded for CVE-2026-89078. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-89078 affect?

CVE-2026-89078 affects GitLab CE/EE 19.2 before 19.2.7, GitLab CE/EE 19.3 before 19.3.3, GitLab CE/EE 19.4 before 19.4.1, Self-hosted GitLab instances running affected versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89078?

Apply vendor patches immediately; audit CI configs, tokens, runners and logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

GitLab CE/EE 19.2 before 19.2.7GitLab CE/EE 19.3 before 19.3.3GitLab CE/EE 19.4 before 19.4.1Self-hosted GitLab instances running affected versions

impact

Authenticated user can execute arbitrary code on GitLab server via a specially crafted CI regex double-free, risking full server compromise and pipeline/artifact theft.

action required

Immediate action required

affected versions

GitLab

affected>= 19.2 and < 19.2.7
affected>= 19.3 and < 19.3.3
affected>= 19.4 and < 19.4.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation: none
automatable: no
technical impact: total

Assessed by CISA 24 Sept 2026 (SSVC 2.0.3).

timeline

23 Sept 2026Published
24 Sept 2026CISA SSVC assessment: exploitation none · same day later
24 Sept 2026Analysed by vulneraibility.com · same day later
30 Oct 2026CVE record last updated · 37 days later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

4 references in the CVE record: 1 exploit, 3 links

Exploithackerone.com /reports/4019059
Linkgitlab.com /gitlab-org/gitlab/-/work_items/628577
Linkdocs.gitlab.com /releases/patches/patch-release-gitlab-19-4-1-released/
Linkruby-lang.org /en/news/2026/10/23/regexp-fixes-for-gitlab-cves/

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free