GitLab · GitLab · published 2026-04-22

CVE-2026-4922Cross-Site Request Forgery (CSRF) in GitLab

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-4922 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 19% of all CVEs. This GitLab vulnerability: CVSS 8.1 (v3.1), a successful attack gives total control of the component. Fixed upstream in GitLab 18.11.1, 18.10.4, 18.9.6. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 18.11.1, 18.10.4, 18.9.6.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.11.1, 18.10.4, 18.9.6

    Upgrade to 18.11.118.10.418.9.6

    Why: CVE-2025-0186: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (20th pct)FIRST EPSS v2026.06.15
CVSS base score8.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA 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.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

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 →