Skip to content
Fencer Intel
medium 5.4

CVE-2026-5309 json

Authorization Bypass Through User-Controlled Key in GitLab

published 4mo ago modified 2mo ago also BIT-gitlab-2026-5309 , EUVD-2026-39175

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami gitlab 18.11.6, 19.0.3, 19.1.1
  • GitLab GitLab 18.11.6, 19.0.3, 19.1.1

Is CVE-2026-5309 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/3628793 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=18.6.0, <18.11.6
>=19.0.0, <19.0.3
>=19.1.0, <19.1.1
18.11.6
19.0.3
19.1.1

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.