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

Improper Authorization in GitLab Rapid Diffs

IdentifiersCVE-2026-2238CWE-863

CVE-2026-2238 is a medium-severity improper authorization vulnerability in GitLab Community Edition and Enterprise Edition Rapid Diffs. It affects all versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. Under certain conditions, improper authorization checks could allow an unauthenticated user to view references to confidential issues within public projects. The issue is an authorization failure in the Rapid Diffs functionality that exposes confidential issue references that should not be visible to unauthenticated users.

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.

Start free trial
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 can result in sensitive information disclosure. Specifically, an unauthenticated attacker may be able to view confidential issue references associated with public projects, revealing the existence or linkage of confidential issues that should remain restricted. Based on the provided information, the impact is limited to unauthorized disclosure rather than code execution or privilege escalation.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting unauthenticated access to public projects where feasible and reviewing use of confidential issues and their references in contexts exposed through Rapid Diffs. Because the root cause is an authorization flaw in application logic, the primary effective mitigation is vendor patching; no complete workaround is provided in the available information.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed version: 18.11.6 or later, 19.0.3 or later, or 19.1.1 or later. GitLab advised self-managed customers to upgrade immediately. GitLab.com was already patched at the time of disclosure, and GitLab Dedicated customers required no action according to the vendor.
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.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
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.
Start free trial
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 activity2

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

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-2238
NVD
nvd.nist.gov/vuln/detail/CVE-2026-2238
MITRE CWE · CWE-863
cwe.mitre.org