Skip to content
major vulnerability· requires attention

Widely used GitLab platform; token theft and repo access affect many orgs; significant disruption risk.

Web

CVE-2025-7659

8.0
High
EPSS 0.19%Patch availableFeb 11, 2026

Unauthenticated token theft and private repo access via GitLab Web IDE validation flaw.

common questions

Is CVE-2025-7659 being exploited?

Not confirmed. CVE-2025-7659 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2025-7659?

CVE-2025-7659 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-7659?

Yes. A fix has been recorded for CVE-2025-7659. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-7659 affect?

CVE-2025-7659 affects GitLab CE/EE < 18.6.6, GitLab CE/EE < 18.7.4, GitLab CE/EE < 18.8.4, GitLab Web IDE. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-7659?

Upgrade to fixed releases (18.6.6+, 18.7.4+, 18.8.4+).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitLab CE/EE < 18.6.6GitLab CE/EE < 18.7.4GitLab CE/EE < 18.8.4GitLab Web IDE
impact

Unauthenticated attackers can steal access tokens and access private repos via Web IDE validation flaw.

action required

Immediate action required

affected versions
GitLab GitLab
  • affected>= 18.2 and < 18.6.6
  • affected>= 18.7 and < 18.7.4
  • affected>= 18.8 and < 18.8.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free