Database/Control plane, storage & DevOps
GitLab: authenticated user can read private CI/CD template files from projects they cannot access
Impact
A missing authorization check lets any signed-in user read private CI/CD template files from projects they have no access to. Shared pipeline templates show how builds and deployments run: runner tags, registry paths, deploy targets, and sometimes hard-coded values. The flaw only reads data. It does not run anything.
Who can reach it
Any authenticated user on the GitLab instance. Affects 13.12 and later.
What to do
Upgrade GitLab to 19.3.9, 19.4.8 or 19.5.6. Self-managed instances need a GitLab upgrade and service restart. Check private templates for embedded secrets and rotate any you find.
References
Related entries
- GitLab: authenticated user can import Git repositories despite administrator import-source restrictionsCVE-2026-108154 · GitLab CE/EE (repository import source restrictions)Medium
- GitLab: authenticated user can read Git LFS objects from restricted projectsCVE-2026-108155 · GitLab CE/EE (Git LFS object authorization)Medium
- Apache Airflow: queued-event deletion checks edit rights on one Dag but clears events for all readable DagsCVE-2026-111453 · Apache Airflow (asset queued-events DELETE endpoint)Medium
- GitLab: authenticated user can read NuGet package metadata that should not be accessibleCVE-2026-115218 · GitLab CE/EE (NuGet package registry)Medium
- GitLab EE: Duo Agent Platform shows unredacted secret values from secret detection findingsCVE-2026-115736 · GitLab EE (Duo Agent Platform, secret detection findings)Medium
- GitLab EE: authenticated user can configure GitLab Duo settings for groups without an eligible licenseCVE-2026-122045 · GitLab EE (GitLab Duo group settings)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.