Database/Control plane, storage & DevOps
GitLab: authenticated user can read Git LFS objects from restricted projects
CVSS 4.3CVE-2026-108155Control plane, storage & DevOpscurated
Impact
An incorrect authorization check lets a signed-in user read Git LFS objects from projects they are not allowed to access. On ML teams, LFS often stores large artifacts such as model weights, datasets and binaries, so the leak can include proprietary models or training data. The flaw only reads data.
Who can reach it
Any authenticated user on the GitLab instance. Affects 8.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.
References
Related entries
- 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
- GitLab: MCP-scoped OAuth token can approve and merge merge requests beyond its scopeCVE-2026-123142 · GitLab CE/EE (MCP-scoped OAuth token authorization)Medium
- GitLab EE: authenticated user can cause a denial of service in Duo usage analytics via crafted inputCVE-2026-125920 · GitLab EE (Duo usage analytics)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.