GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: injected content can lead to account takeover in versions from 14.10

CVSS 9.6CVE-2025-9642Control plane, storage & DevOpscurated

Impact

An attacker can inject malicious content into GitLab CE/EE that may lead to takeover of another user's account; the CVSS vector requires one click from the victim and reports a scope change. Self-managed GitLab is usually the thing that holds the fleet's CI credentials, container-registry push rights and GitOps deploy keys, so an account takeover there is not contained to a code-review tool - it is a route to the images and manifests that land on GPU nodes. The record is thin on mechanism and the GitLab issue is the only detail available. Affected: all versions from 14.10 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1.

Who can reach it

Remote, over the GitLab web interface, against a logged-in user who must interact with the injected content. The vector reports no privileges required for the attacker beyond being able to place the content.

What to do

Upgrade self-managed GitLab to 18.2.7, 18.3.3 or 18.4.1 depending on your branch, then restart the application - a standard GitLab upgrade window, no node reboots. After patching, review admin and CI-service accounts for unexpected sessions, tokens and runner registrations, and rotate anything a taken-over maintainer could have reached. GitLab.com is already patched.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.