Database/Control plane, storage & DevOps
GitLab: developer-role user can replace package file content and hide packages from owners
Impact
Improper authorization in the Generic Package Registry lets a user with only developer-role permissions substitute the content of an existing package file and hide packages from their owners. Where the registry is the distribution point for internal artifacts - driver bundles, container build inputs, model or dataset archives pulled by cluster jobs - this is a supply-chain integrity problem inside the organisation: consumers fetch the same package name and version and get different bytes, and the owner does not see the package to notice. The flaw has been present since GitLab 13.9, so any affected instance has had a long exposure window. It needs a developer account on the project, not an anonymous attacker.
Who can reach it
An authenticated GitLab user with developer-role permissions on the project, over the network to the GitLab instance.
What to do
Upgrade self-managed GitLab to 19.1.8, 19.2.6, or 19.3.2. Package upgrade and service restart on the GitLab host. Given the long exposure window, verify checksums of generic packages that cluster jobs consume against a trusted copy rather than assuming the registry contents are intact.
References
Related entries
- Apache Airflow: /assets/events returns asset events for every DAG, ignoring per-DAG access controlCVE-2026-75158 · Apache Airflow core API (/assets/events endpoint)Medium
- Jenkins core: crafted XML submission lets a read-only user create user objects on the controllerCVE-2026-84646 · Jenkins core (XML deserialization, user objects as nested field values)Medium
- Jenkins core: unescaped map keys let a user inject arbitrary fields into JSON and Python API responsesCVE-2026-84655 · Jenkins core (REST API JSON and Python serialization, unescaped map keys)Medium
- Jenkins core: missing permission check exposes build parameters of jobs a user cannot otherwise seeCVE-2026-84656 · Jenkins core (build parameter access, missing Item/Read permission check)Medium
- Jenkins Script Security Plugin: form submission exposes the script approval configuration to attackersCVE-2026-84658 · Jenkins Script Security Plugin (script approval configuration)Medium
- Jenkins Script Security Plugin: missing permission check lets attackers disable global sandbox enforcementCVE-2026-84659 · Jenkins Script Security Plugin (global sandbox enforcement setting)Medium
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.