GitLab · GitLab · published 2025-12-11

CVE-2025-11984Authentication Bypass Using an Alternate Path or Channel in GitLab

Routine No exploitation evidence; EPSS 0.4%.

CVE-2025-11984 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 36% of all CVEs. This GitLab vulnerability: CVSS 6.8 (v3.1), a successful attack gives total control of the component. Fixed upstream in GitLab 18.6.2, 18.5.4, 18.4.6. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 18.6.2, 18.5.4, 18.4.6.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.6.2, 18.5.4, 18.4.6

    Upgrade to 18.6.218.5.418.4.6

    Why: Vendor security release for server software (most severe: CVE-2025-12716).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (37th pct)FIRST EPSS v2026.06.15
CVSS base score6.8 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 13.1 before 18.4.6, 18.5 before 18.5.4, and 18.6 before 18.6.2 that could have allowed an authenticated user to bypass WebAuthn two-factor authentication by manipulating the session state under certain conditions.

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 →