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

Exp

An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.3 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. A security vulnerability allows attackers to bypass Device OAuth flow protections, enabling authorization form submission through minimal user interaction.

Published: 2025-05-09 Last update: 2025-08-08 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-0549 is rated Exploit Available (50.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.32%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-0549

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-0549

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.32% +0.26%
2 2026-03-05 0.01% 0.06% +0.05%
3 2025-05-10 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-0549

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 5.2 [email protected]

Weakness enumeration for CVE-2025-0549

OS Trackers for CVE-2025-0549

vendor priority summary link
debian not yet assigned CVE-2025-0549 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): open 1. https://security-tracker.debian.org/tracker/CVE-2025-0549
ubuntu medium CVE-2025-0549 medium priority: Ubuntu including 1 source packages (gitlab), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, upstream, xenial): DNE 5, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-0549

Affected software / configurations for CVE-2025-0549

Vendor Product Version Raw CPE
gitlab gitlab >= 17.3.0, < 17.9.8 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 17.3.0, < 17.9.8 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 17.10.0, < 17.10.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 17.10.0, < 17.10.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 17.11.0, < 17.11.2 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 17.11.0, < 17.11.2 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

References for CVE-2025-0549

cvelogic Threat Intelligence