Skip to content
Fencer Intel
medium 4.3

CVE-2025-0290 json

Loop with Unreachable Exit Condition ('Infinite Loop') in GitLab

published last yr. modified 4mo ago also BIT-gitlab-2025-0290 , EUVD-2025-1582

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

Summary

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.0 prior to 17.5.5, from 17.6 prior to 17.6.3, and from 17.7 prior to 17.7.1. Under certain conditions, processing of CI artifacts metadata could cause background jobs to become unresponsive.

Patch / fix

  • bitnami gitlab 17.6.4, 17.7.2, 17.8.0
  • GitLab GitLab 17.6.4, 17.7.2, 17.8.0

Is CVE-2025-0290 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
last yr.

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=15.0.0, <17.6.4
>=17.7.0, <17.7.2
>=17.8.0, <17.8.0
17.6.4
17.7.2
17.8.0

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition
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.

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