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

HTML injection denial of service in GitLab CI/CD Catalog

IdentifiersCVE-2026-10733CWE-79

CVE-2026-10733 is an HTML injection issue in GitLab Community Edition (CE) and Enterprise Edition (EE) affecting all versions from 17.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. The flaw is described as improper sanitization in the CI/CD Catalog page. By supplying crafted content that is not properly sanitized before being rendered or processed by the Catalog page, an authenticated user can trigger a denial-of-service condition affecting that page. The available source material identifies the issue as an HTML injection bug and attributes the root cause to improper sanitization, but does not provide lower-level implementation details such as the exact vulnerable function or code path.

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 attacker to cause denial of service on the GitLab CI/CD Catalog page. Based on the provided information, the impact is limited to availability degradation or disruption of that page rather than direct code execution, privilege escalation, or data exfiltration.

Mitigation

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

If immediate upgrade is not possible, reduce exposure by limiting access to the affected GitLab instance to trusted authenticated users and monitoring for malformed or suspicious content affecting the CI/CD Catalog page. However, the provided content does not describe any vendor-supported workaround, so upgrading is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed version. Patched releases identified in the provided content are 18.10.8, 18.11.5, and 19.0.2 or later, depending on the deployment branch. GitLab strongly recommended that self-managed installations upgrade immediately. The release may include database migrations that can cause downtime on single-node instances, so upgrade planning should account for that.
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 activity2

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