Medium

Improper access control information disclosure in GitLab CE/EE issue description rendering

IdentifiersCVE-2026-5377CWE-284

CVE-2026-5377 is an improper access control vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). It affects all versions from 18.11 before 18.11.1. According to the provided content, the flaw exists in the issue description rendering process and could allow an authenticated user to access the titles of confidential or private issues in public projects. The issue is therefore an authorization failure during rendering that exposes restricted issue metadata to a user who should not be permitted to view it.

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 allows an authenticated user to disclose sensitive information by viewing titles of confidential or private issues in public projects. While the provided content does not indicate arbitrary code execution or privilege escalation, issue titles can contain sensitive operational, security, or business information, resulting in unauthorized information disclosure and potential intelligence gathering for further attacks.

Mitigation

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

If immediate upgrade is not possible, reduce exposure by limiting access for untrusted authenticated users, reviewing permissions for public projects that contain confidential or private issues, and avoiding inclusion of sensitive details in issue titles until the fix is applied. Definitive mitigation information beyond upgrade is not available in the provided content.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to version 18.11.1 or later. The provided content states that GitLab remediated the issue in 18.11.1.

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.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

2 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

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 activity1

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

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-5377

NVD

nvd.nist.gov/vuln/detail/CVE-2026-5377

MITRE CWE · CWE-284

cwe.mitre.org

Vendor Advisory

about.gitlab.com/releases/2026/04/22/patch-release-gitlab-18-11-1-released

Permissions Required

hackerone.com/reports/3640688