CVE-2026-5309

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH 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.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 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(high)
EPSS
6.8%
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.org / GitLab · GitLab

https://gitlab.com/gitlab-org/gitlab/-/work_items/595468
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(1)

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 24× in last 7d / 39× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 11:18 UTCEG score recompute
  4. 2026-07-06 11:18 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 11:02 UTCEG score recompute
  8. 2026-07-05 11:02 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 11:04 UTCEG score recompute
  12. 2026-07-04 11:04 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 11:07 UTCEG score recompute
  16. 2026-07-03 11:07 UTCGHSA enrichment
  17. 2026-07-02 11:00 UTCEG score recompute
  18. 2026-07-02 11:00 UTCGHSA enrichment
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 10:55 UTCEG score recompute
  21. 2026-07-01 10:55 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 10:57 UTCEG score recompute
  24. 2026-06-30 10:57 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 14 more
  1. 2026-06-29 10:51 UTCEG score recompute
  2. 2026-06-29 10:51 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 10:54 UTCEG score recompute
  5. 2026-06-28 10:54 UTCGHSA enrichment
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 10:56 UTCEG score recompute
  8. 2026-06-27 10:56 UTCGHSA enrichment
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 10:58 UTCEG score recompute
  11. 2026-06-26 10:58 UTCGHSA enrichment
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 06:07 UTCEG score recompute
  14. 2026-06-25 06:05 UTCNVD updatefirst tracked

Related CVEs(same CWE)

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 6.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs