Skip to main content
Menu
CVEs

CVE

GitLab missing authorization exposes NuGet package metadata

CVE-2026-115218EUVD-2026-126852GHSA-9G35-379W-RQ6W

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

4.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 19.3.9, 19.4.8, 19.5.6
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.

Published
Last modified
Reference
Last checked
0.18% · 7th percentile
21/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

GitLab CE and EE have a missing authorization flaw that, under certain conditions, lets a logged-in user read NuGet package metadata they should not be able to access. The attacker needs only low-privilege login and can reach the flaw remotely over the network.

Written by a model from the sources below. Verify against them.

Original description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read NuGet package metadata that should not have been accessible due to missing authorization checks.

cve.now Index

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach14/20Affects GitLab (an enterprise product or network appliance)
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115218 (Missing Authorization in GitLab), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115218 (entry last updated 2026-11-17):
Affected:
- GitLab GitLab: from 13.8, fixed in 19.3.9; from 19.4, fixed in 19.4.8; from 19.5, fixed in 19.5.6
Fixed versions: 19.3.9, 19.4.8, 19.5.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115218 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115218 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.com/gitlab-org/gitlab/-/work_items/602409
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115218
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115218"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • GitLab GitLab

    From 13.8 · fixed in 19.3.9; From 19.4 · fixed in 19.4.8; From 19.5 · fixed in 19.5.6

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-115218

Is CVE-2026-115218 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-115218?

GitLab: from 13.8 before 19.3.9; from 19.4 before 19.4.8; from 19.5 before 19.5.6.Source: cve.now feed data

How do I fix CVE-2026-115218?

Upgrade to a fixed version: 19.3.9, 19.4.8, 19.5.6.Source: cve.now feed data

More CVEs