Database/Control plane, storage & DevOps
GitLab: authenticated user can read NuGet package metadata that should not be accessible
CVSS 4.3CVE-2026-115218Control plane, storage & DevOpscurated
Impact
A missing authorization check in the NuGet package registry lets a signed-in user read package metadata they should not see. Only metadata is exposed. The record does not say that package contents can be read or changed.
Who can reach it
Any authenticated user on the GitLab instance. Affects 13.8 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
- 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
- GitLab EE: Duo Workflow session can start with more privileges than its foundational flow declaresCVE-2026-128849 · GitLab EE (Duo Workflow / foundational flows)Medium
- GitLab EE: developer-role user can bypass admin AI tool governance controls in a governed namespaceCVE-2026-129253 · GitLab EE (AI tool governance controls for workflows)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.