CVE-2025-0549

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2025-05-09. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
24.9%
KEV
Not listed

Published

May 9, 2025

Last Modified

August 8, 2025

References (2)

Vendor Advisories for CVE-2025-0549(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 01:51 UTCOSV refresh
  2. 2026-07-06 16:26 UTCEPSS rescore
  3. 2026-07-06 16:26 UTCEPSS rescore
  4. 2026-07-06 02:22 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:30 UTCEPSS rescore
  7. 2026-07-04 06:30 UTCEPSS rescore
  8. 2026-07-02 17:00 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:21 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 40 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-19 19:25 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 13:05 UTCOSV refresh
  6. 2026-06-17 17:52 UTCEPSS rescore
  7. 2026-06-16 17:52 UTCEPSS rescore
  8. 2026-06-15 17:48 UTCEPSS rescore
  9. 2026-06-15 17:48 UTCEPSS rescore
  10. 2026-06-14 23:17 UTCEPSS rescore
  11. 2026-06-13 22:59 UTCEPSS rescore
  12. 2026-06-12 23:11 UTCEPSS rescore
  13. 2026-06-12 23:11 UTCEPSS rescore
  14. 2026-06-11 13:59 UTCEPSS rescore
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 22:18 UTCEPSS rescore
  17. 2026-06-10 13:21 UTCEPSS rescore
  18. 2026-06-10 13:21 UTCEPSS rescore
  19. 2026-06-08 14:16 UTCEPSS rescore
  20. 2026-06-08 14:16 UTCEPSS rescore
  21. 2026-06-07 15:24 UTCEPSS rescore
  22. 2026-06-06 13:47 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 06:10 UTCEPSS rescore
  27. 2026-06-05 06:09 UTCEPSS rescore
  28. 2026-06-04 13:11 UTCEPSS rescore
  29. 2026-06-04 13:11 UTCEPSS rescore
  30. 2026-06-02 20:12 UTCEPSS rescore
  31. 2026-06-02 20:12 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-06-01 13:51 UTCEPSS rescore
  34. 2026-05-31 22:30 UTCEPSS rescore
  35. 2026-05-31 22:30 UTCEPSS rescore
  36. 2026-05-31 00:16 UTCEPSS rescore
  37. 2026-05-31 00:16 UTCEPSS rescore
  38. 2026-05-30 05:46 UTCEG score recompute
  39. 2026-05-30 05:46 UTCGHSA enrichment
  40. 2026-05-29 13:43 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-0549?
CVE-2025-0549 is a medium vulnerability published on May 9, 2025. 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…
When was CVE-2025-0549 disclosed?
CVE-2025-0549 was first published in the National Vulnerability Database on May 9, 2025, with the most recent update on August 8, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-0549 actively exploited?
CVE-2025-0549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-0549?
CVE-2025-0549 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2025-0549?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-0549, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-0549

Explore →

Is Your Infrastructure Affected by CVE-2025-0549?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs