GitLab · GitLab · published 2026-05-14

CVE-2026-3073Authorization Bypass Through User-Controlled Key in GitLab

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-3073 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 18% of all CVEs. This GitLab vulnerability: CVSS 4.3 (v3.1). Fixed upstream in GitLab 18.11.3, 18.10.6, 18.9.7. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 18.11.3, 18.10.6, 18.9.7.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.11.3, 18.10.6, 18.9.7

    Upgrade to 18.11.318.10.618.9.7

    Why: Vendor security release for server software (most severe: CVE-2026-6073).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (18th pct)FIRST EPSS v2026.06.15
CVSS base score4.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to bypass PyPI package protection rules and upload restricted packages due to improper authorization checks.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →