CVE-2026-5309

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

Score 5.4 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without authorization.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

GitLab Patch Release: 19.1.1, 19.0.3, 18.11.6 | GitLab Docs

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

Vendor Advisories for CVE-2026-5309(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-08-28 02:57 UTCEG score recompute
  2. 2026-08-28 02:57 UTCGHSA enrichment
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-24 13:17 UTCEG score recompute
  7. 2026-08-24 13:17 UTCGHSA enrichment
  8. 2026-08-23 10:59 UTCEG score recompute
  9. 2026-08-23 10:59 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 11:02 UTCEG score recompute
  12. 2026-08-22 11:02 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 07:15 UTCEG score recompute
  15. 2026-08-21 07:15 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 07:12 UTCEG score recompute
  18. 2026-08-20 07:12 UTCGHSA enrichment
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-19 01:37 UTCEG score recompute
  21. 2026-08-19 01:37 UTCGHSA enrichment
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 02:59 UTCEG score recompute
  25. 2026-08-17 02:59 UTCGHSA enrichment
Show 75 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 03:02 UTCEG score recompute
  3. 2026-08-16 03:02 UTCGHSA enrichment
  4. 2026-08-15 03:05 UTCEG score recompute
  5. 2026-08-15 03:05 UTCGHSA enrichment
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 03:07 UTCEG score recompute
  8. 2026-08-14 03:07 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 03:10 UTCEG score recompute
  11. 2026-08-13 03:10 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 03:13 UTCEG score recompute
  14. 2026-08-12 03:13 UTCGHSA enrichment
  15. 2026-08-11 03:15 UTCEG score recompute
  16. 2026-08-11 03:15 UTCGHSA enrichment
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 03:18 UTCEG score recompute
  19. 2026-08-10 03:18 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 03:21 UTCEG score recompute
  22. 2026-08-09 03:21 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 03:24 UTCEG score recompute
  25. 2026-08-08 03:24 UTCGHSA enrichment
  26. 2026-08-07 03:27 UTCEG score recompute
  27. 2026-08-07 03:27 UTCGHSA enrichment
  28. 2026-08-06 13:47 UTCEPSS rescore
  29. 2026-08-06 03:29 UTCEG score recompute
  30. 2026-08-06 03:29 UTCGHSA enrichment
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-05 03:32 UTCEG score recompute
  33. 2026-08-05 03:32 UTCGHSA enrichment
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 10:39 UTCEPSS rescore
  36. 2026-08-04 03:12 UTCEG score recompute
  37. 2026-08-04 03:12 UTCGHSA enrichment
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-03 03:15 UTCGHSA enrichment
  40. 2026-08-02 03:18 UTCEG score recompute
  41. 2026-08-02 03:17 UTCGHSA enrichment
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-08-01 03:19 UTCGHSA enrichment
  45. 2026-07-31 03:21 UTCEG score recompute
  46. 2026-07-31 03:21 UTCGHSA enrichment
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 02:06 UTCEG score recompute
  49. 2026-07-30 02:06 UTCGHSA enrichment
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-29 00:28 UTCEG score recompute
  53. 2026-07-29 00:27 UTCGHSA enrichment
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-27 17:30 UTCEG score recompute
  56. 2026-07-27 17:30 UTCGHSA enrichment
  57. 2026-07-27 14:14 UTCEPSS rescore
  58. 2026-07-26 15:16 UTCEG score recompute
  59. 2026-07-26 15:16 UTCGHSA enrichment
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-25 14:18 UTCEPSS rescore
  64. 2026-07-24 14:18 UTCEPSS rescore
  65. 2026-07-24 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 03:19 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-22 14:08 UTCEPSS rescore
  71. 2026-07-21 15:25 UTCEPSS rescore
  72. 2026-07-21 15:25 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5309?
CVE-2026-5309 is a medium vulnerability published on June 25, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without…
When was CVE-2026-5309 disclosed?
CVE-2026-5309 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5309 actively exploited?
CVE-2026-5309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-5309?
CVE-2026-5309 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-5309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5309, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-5309

Explore →

Is Your Infrastructure Affected by CVE-2026-5309?

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