CVE-2026-100104: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.3 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an...
Low CVSS 3.5
- CVE id
- CVE-2026-100104
- Published
- Last modified
Affected packages
How to fix it
GitLab CE (Runtimes and servers)
Upgrade GitLab CE to the fixed release of the line you run: 19.2.8, 19.3.5, 19.4.2.
gitlab-rake gitlab:env:info
- Upgrade your self-managed GitLab (the gitlab/gitlab-ce image tag or the gitlab-ce package) to the patched release of your series.
GitLab EE (Runtimes and servers)
Upgrade GitLab EE to the fixed release of the line you run: 19.2.8, 19.3.5, 19.4.2.
gitlab-rake gitlab:env:info
- Upgrade your self-managed GitLab EE (the gitlab/gitlab-ee image tag or the gitlab-ee package) to the patched release of your series.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.3 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to perform server-side request forgery and reach internal network resources due to a time-of-check to time-of-use race condition in URL validation during repository import operations.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.