Skip to main content
Mallory
UnratedVulnerability

CVE-2025-8094: Improper Handling of Permissions in GitLab Project API

Updated 4 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-8094CWE-284

CVE-2025-8094 is a high-severity improper handling of permissions vulnerability in the GitLab Community Edition and Enterprise Edition project API. Under certain conditions, authenticated users with maintainer privileges could manipulate shared infrastructure resources beyond their intended access level through the project API. The flaw stems from insufficient permission enforcement in API operations governing access to shared CI/CD-related infrastructure resources, allowing a maintainer to act outside the intended authorization boundary. GitLab addressed the issue by refining permission checks within the project API to enforce proper access controls.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an authenticated maintainer to interfere with shared infrastructure resources used by CI/CD workflows and cause denial of service affecting other users’ pipelines. The primary security impact is disruption of availability for CI/CD operations belonging to other users or projects that rely on the affected shared resources.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting maintainer access to trusted users only, reviewing projects that can interact with shared CI/CD infrastructure, and increasing monitoring for abnormal pipeline failures or administrative actions involving shared infrastructure resources through the project API. Because the issue is rooted in server-side authorization logic, mitigation is only partial until the fixed version is deployed.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. Patched versions include 18.0.6, 18.1.4, and 18.2.2. Self-managed deployments should update to the appropriate patched version on their supported branch. The vendor indicated these patch releases include the permission-check corrections required to prevent maintainers from manipulating shared infrastructure resources beyond their authorized scope.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-8094 exploited in the wild?
As of Jul 31, 2026, Mallory has no reports of CVE-2025-8094 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-8094?
As of Jul 31, 2026, Mallory has found no public exploit for CVE-2025-8094.
Is there a patch for CVE-2025-8094?
Upgrade GitLab CE/EE to a fixed release. Patched versions include 18.0.6, 18.1.4, and 18.2.2.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.