Medium

XSS in GitLab CE/EE Kubernetes proxy endpoint

IdentifiersCVE-2025-0475CWE-79· Improper Neutralization of Input…

CVE-2025-0475 is a high-severity cross-site scripting vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 15.10 before 17.7.6, 17.8 before 17.8.4, and 17.9 before 17.9.1. The flaw is in a Kubernetes proxy endpoint, where a proxy feature can allow unintended content rendering under specific circumstances. This rendering behavior can cause attacker-controlled content to be interpreted in a victim’s browser, resulting in cross-site scripting.

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 cause arbitrary script execution in the context of a victim user’s browser session within GitLab. Depending on the victim’s privileges, this can enable theft of session data, execution of actions as the victim, access to sensitive data exposed through the web application, and compromise of integrity within the affected GitLab instance. The published CVSS vector indicates scope change and high confidentiality and integrity impact, with no direct availability impact.

Mitigation

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

If immediate patching is not possible, reduce exposure to the vulnerable Kubernetes proxy functionality where operationally feasible, restrict access to GitLab to trusted users, and minimize opportunities for lower-privileged users to supply content that could be rendered through the affected proxy path. Standard browser-side controls such as CSP may reduce exploit reliability in some deployments, but they are not a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 17.7.6, 17.8.4, 17.9.1, or a later patched version. Self-managed installations should be updated immediately to a release that includes the fix. GitLab.com was already running a patched version at the time of disclosure.

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, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

gitlab releasesNews

Feb 26, 2025

GitLab Patch Release: 17.9.1, 17.8.4, 17.7.6 | GitLab Docs

A high-severity cross-site scripting vulnerability in GitLab CE/EE's k8s proxy endpoint that can allow unintended content rendering under specific circumstances.

gitlab releasesNews

Mar 18, 2026

GitLab Patch Release: 17.9.1, 17.8.4, 17.7.6 | GitLab

A high-severity cross-site scripting issue in GitLab CE/EE’s Kubernetes proxy endpoint where a proxy feature could allow unintended content rendering leading to XSS under specific circumstances.

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 activity