Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Information disclosure via GraphQL queries in GitLab EE

IdentifiersCVE-2025-9484CWE-200

GitLab EE contains an information disclosure vulnerability affecting all versions from 16.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3. Under certain circumstances, specific GraphQL queries could allow an authenticated user to access other users' email addresses. Based on the provided content, the issue is limited to disclosure of email address data through GraphQL query paths and does not indicate code execution or privilege escalation.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows an authenticated user to disclose other users' email addresses that should not have been exposed to them. The primary impact is loss of confidentiality of user PII/contact information within affected GitLab EE instances.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting access to GraphQL endpoints to only trusted authenticated users, reviewing and restricting roles/accounts that can query user-related data, and monitoring for unusual GraphQL queries targeting user profile fields such as email addresses. No vendor-specific workaround beyond upgrading was provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed version: 18.8.9, 18.9.5, 18.10.3, or later, depending on the deployed release train. GitLab urged self-managed customers to upgrade immediately. GitLab.com was already patched, and GitLab Dedicated customers did not need to take action according to the provided content.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.