MediumPublic exploit

CSRF token exfiltration in GitLab CE/EE Kubernetes Agent Server integration

IdentifiersCVE-2023-7045CWE-352· Cross-Site Request Forgery (CSRF)

CVE-2023-7045 is a cross-site request forgery vulnerability in GitLab Community Edition and Enterprise Edition affecting versions 13.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. The flaw is associated with Kubernetes cluster integration and can be leveraged through the Kubernetes Agent Server (KAS) to exfiltrate anti-CSRF tokens. The issue allows a forged cross-site request in an authenticated user context to cause disclosure of CSRF protection material, weakening request integrity protections for subsequent actions.

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 expose anti-CSRF tokens from an authenticated GitLab user via KAS. Disclosure of these tokens can undermine GitLab's CSRF defenses and enable follow-on unauthorized actions performed in the victim's authenticated session context, with potential confidentiality and integrity impact depending on the victim's privileges and reachable application functionality.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting or disabling vulnerable Kubernetes integration paths involving KAS where operationally feasible, restricting access to GitLab to trusted origins and users, and minimizing opportunities for authenticated users to be induced to visit attacker-controlled content. Additional defensive measures include enforcing strong session hygiene and monitoring for suspicious cross-origin interactions involving Kubernetes integration features. Complete mitigation requires upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. Patched versions include 16.10.6, 16.11.3, and 17.0.1 or later. Self-managed deployments should update to one of these releases or a newer maintained version that includes the fix.

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

Apr 25, 2024

GitLab Patch Release: 17.0.1, 16.11.3, 16.10.6 | GitLab Docs

A medium-severity GitLab CE/EE cross-site request forgery vulnerability in Kubernetes cluster integration that can allow exfiltration of anti-CSRF tokens via KAS.

gitlab releasesNews

Mar 18, 2026

GitLab Patch Release: 17.0.1, 16.11.3, 16.10.6 | GitLab

Medium-severity CSRF issue in GitLab Kubernetes cluster integration that can allow exfiltration of anti-CSRF tokens via KAS.

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