CVE-2026-89078

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-24. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-85736 (ENISA EUVD) · GHSA-9chr-4x58-948m (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (GitLab Inc.) states them: "Upgrade to versions 19.2.7, 19.3.3, 19.4.1 or above."

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.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 23, 2026

Last Modified

October 31, 2026

Advisory Details (3)

Auto-updated Nov 7, 2026
Patch available.
Web page

Regexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264 | Ruby

https://www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves/
Web page

Work items · GitLab.org / GitLab · GitLab

https://gitlab.com/gitlab-org/gitlab/-/work_items/628577
Web page

GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruby:3.3-9080020261105110750.92026-11-09redhat
redhatruby-0:3.3.13-16.el10_22026-11-09redhat
redhatruby-0:3.0.7-170.el9_82026-11-09redhat
redhatopenvox-agent-0:8.32.0-1.el9sat2026-11-05redhat
redhatpython-pyyaml-0:6.0.1-1.el9pc2026-11-05redhat
redhatruby4-0-main-4.0.9-41.hum12026-10-24redhat
redhatruby3-3-main-3.3.13-23.8.hum12026-10-24redhat
redhatruby3-4-main-3.4.12-33.1.hum12026-10-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • every version up to 3.3.13-r0: fixed in 3.3.13-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • every version up to 3.4.12-r0: fixed in 3.4.12-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • every version up to 3.4.12-r0: fixed in 3.4.12-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
ruby—
  • every version up to 3.4.12-r0: fixed in 3.4.12-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby3.13.1.2-7 ... 3.1.2-8.5 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2
  • every version up to 3.3.13-0+deb13u1: fixed in 3.3.13-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 81× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 270 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 18:41 UTCEchelonGraph re-scored
  2. 2026-11-12 18:41 UTCVendor advisory
  3. 2026-11-12 18:41 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-11 20:51 UTCEchelonGraph re-scored
  6. 2026-11-11 20:51 UTCVendor advisory
  7. 2026-11-11 20:51 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  8. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-11-10 22:54 UTCEchelonGraph re-scored
  10. 2026-11-10 22:54 UTCVendor advisory
  11. 2026-11-10 22:54 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  12. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-11-10 00:43 UTCEchelonGraph re-scored
  14. 2026-11-10 00:43 UTCVendor advisory
  15. 2026-11-10 00:43 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-09 02:53 UTCEchelonGraph re-scored
  18. 2026-11-09 02:53 UTCVendor advisory
  19. 2026-11-09 02:53 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  20. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-11-08 05:04 UTCEchelonGraph re-scored
  22. 2026-11-08 05:04 UTCVendor advisory
  23. 2026-11-08 05:04 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  24. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-11-07 07:14 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 07:14 UTCVendor advisory
  2. 2026-11-07 07:14 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  3. 2026-11-06 21:25 UTCOSV refresh
  4. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-06 09:22 UTCEchelonGraph re-scored
  6. 2026-11-06 09:22 UTCVendor advisory
  7. 2026-11-06 09:22 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  8. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-11-05 11:32 UTCEchelonGraph re-scored
  10. 2026-11-05 11:32 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-11-04 13:42 UTCEchelonGraph re-scored
  13. 2026-11-04 13:42 UTCVendor advisory
  14. 2026-11-04 13:42 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  15. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-11-03 15:52 UTCVendor advisory
  17. 2026-11-03 15:52 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  18. 2026-11-02 18:02 UTCEchelonGraph re-scored
  19. 2026-11-02 18:02 UTCVendor advisory
  20. 2026-11-02 18:02 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-11-01 20:12 UTCEchelonGraph re-scored
  23. 2026-11-01 20:12 UTCVendor advisory
  24. 2026-11-01 20:11 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  26. 2026-10-31 22:21 UTCEchelonGraph re-scored
  27. 2026-10-31 22:21 UTCVendor advisory
  28. 2026-10-31 22:21 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  29. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  30. 2026-10-31 00:26 UTCEchelonGraph re-scored
  31. 2026-10-31 00:26 UTCVendor advisory
  32. 2026-10-31 00:26 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  33. 2026-10-30 23:29 UTCEchelonGraph re-scored
  34. 2026-10-30 23:29 UTCVendor advisory
  35. 2026-10-30 23:29 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  36. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-10-30 11:21 UTCEchelonGraph re-scored
  38. 2026-10-30 11:21 UTCVendor advisory
  39. 2026-10-30 11:21 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  40. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-10-29 13:32 UTCEchelonGraph re-scored
  42. 2026-10-29 13:32 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  43. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-10-28 15:42 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  45. 2026-10-27 17:52 UTCEchelonGraph re-scored
  46. 2026-10-27 17:52 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  47. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-10-26 20:02 UTCEchelonGraph re-scored
  49. 2026-10-26 20:02 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  50. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-10-25 20:13 UTCEchelonGraph re-scored
  52. 2026-10-25 20:13 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  53. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  54. 2026-10-25 13:53 UTCEchelonGraph re-scored
  55. 2026-10-24 22:21 UTCEchelonGraph re-scored
  56. 2026-10-24 22:21 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  57. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  58. 2026-10-24 00:32 UTCEchelonGraph re-scored
  59. 2026-10-24 00:32 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  60. 2026-10-23 17:42 UTCEchelonGraph re-scored
  61. 2026-10-23 17:42 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  62. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  63. 2026-10-22 19:51 UTCEchelonGraph re-scored
  64. 2026-10-22 19:51 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  65. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  66. 2026-10-21 22:01 UTCEchelonGraph re-scored
  67. 2026-10-21 22:01 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  68. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  69. 2026-10-21 00:00 UTCEchelonGraph re-scored
  70. 2026-10-21 00:00 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  71. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  72. 2026-10-20 02:04 UTCEchelonGraph re-scored
  73. 2026-10-20 02:03 UTCGHSA enrichmentGHSA-9chr-4x58-948m · GitHub severity CRITICAL · GitHub CVSS 9.9
  74. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  75. 2026-10-19 01:14 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-89078?
CVE-2026-89078 is a critical-severity vulnerability; its CVE record was published on September 23, 2026. 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…
When was the CVE record for CVE-2026-89078 published?
The CVE record for CVE-2026-89078 was published on September 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 31, 2026; the record at its source may have been updated since.
Is CVE-2026-89078 actively exploited?
CVE-2026-89078 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89078?
CVE-2026-89078 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89078?
A fix for CVE-2026-89078 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (GitLab Inc.) states them: "Upgrade to versions 19.2.7, 19.3.3, 19.4.1 or above." The vendor advisories EchelonGraph has for CVE-2026-89078 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89078

Explore →

Is Your Infrastructure Affected by CVE-2026-89078?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.