GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: upstream repository owner can poison cached Maven packages of other upstreams in a virtual registry

CVSS 5.9CVE-2026-112203Control plane, storage & DevOpscurated

Impact

Someone who controls one upstream repository behind a GitLab Maven virtual registry can change the cached packages that belong to other upstreams in the same registry, because GitLab does not validate upstream responses properly. Builds that pull dependencies through that registry can then receive altered artifacts. That is a supply-chain path into anything those builds produce or deploy. Confidentiality and availability are not affected.

Who can reach it

No GitLab authentication needed. The attacker must control an upstream repository that a GitLab EE Maven virtual registry is configured to use. Network-reachable, high attack complexity.

What to do

Upgrade GitLab EE to 19.3.9, 19.4.8 or 19.5.6 or later, which restarts the GitLab services. Review which upstreams each Maven virtual registry trusts. Clearing caches that may already be poisoned is a reasonable precaution, but the advisory does not cover it.

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.