Skip to content
Fencer Vulns
medium 5.0

CVE-2025-5819 json

Incorrect Permission Assignment for Critical Resource in GitLab

published 2025-08-13 14 mo ago modified 2026-06-17 4 mo ago also BIT-gitlab-2025-5819 , EUVD-2025-24599

cvss
5.0
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 21%
public exploits
0
none known

Summary

An issue has been discovered in GitLab CE/EE affecting all versions from 15.7 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed authenticated users with developer access to obtain ID tokens for protected branches under certain circumstances.

Patch / fix

  • bitnami gitlab 18.0.6, 18.1.4, 18.2.2
  • GitLab GitLab 18.0.6, 18.1.4, 18.2.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
14 mo ago

Exploit prediction

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

Exploits and checks

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=15.7.0, <18.0.6
>=18.1.0, <18.1.4
>=18.2.0, <18.2.2
18.0.6
18.1.4
18.2.2

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource
Technology feeds

References

Sources

Fencer Vulns 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.