Skip to content
Fencer Intel
low 3.5

CVE-2025-12506 json

Use of Incorrectly-Resolved Name or Reference in GitLab

published 4mo ago modified last mo. also BIT-gitlab-2025-12506 , EUVD-2025-210442

cvss
3.5
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 26%
public exploits
0
none known

Summary

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to create a repository where the content displayed in the web interface differed from the content available for download, due to improper handling of Git reference name resolution.

Patch / fix

  • bitnami gitlab 18.11.7, 19.0.4, 19.1.2
  • GitLab GitLab 18.11.7, 19.0.4, 19.1.2

Is CVE-2025-12506 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.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=16.5.0, <18.11.7
>=19.0.0, <19.0.4
>=19.1.0, <19.1.2
18.11.7
19.0.4
19.1.2

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-706 Use of Incorrectly-Resolved Name or Reference
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.