CVE-2024-4835VulnerabilityPublished 29 May 2024Updated 10 Sep 2026

CVE-2024-4835: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 17.0.1 : patch gitlab soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.0.1, 16.11.3, 16.10.6

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 17.0.1, 16.11.3 or 16.10.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.11.0 <16.10.6 >=16.11.0 <16.11.3 >=17.0.0 <17.0.1	Fixed in 16.10.6 16.11.3 17.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading GitLab to version 16.10.6, 16.11.3, or 17.0.1 or later. Since patches are available, remediation should be performed promptly to mitigate the risk.

Description

A cross-site scripting (XSS) vulnerability exists in GitLab versions 15.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. This flaw allows attackers to inject malicious scripts into web pages, potentially enabling the exfiltration of sensitive user information. The vulnerability has been assigned CVE-2024-4835 and is rated with high severity. Official patches addressing this issue are available in versions 16.10.6, 16.11.3, and 17.0.1.

Impact

Exploitation of this XSS vulnerability could allow attackers to execute arbitrary scripts in the context of the affected GitLab web application, potentially leading to the theft of sensitive user data. No known exploits in the wild have been reported at this time.

Summary

CVE-2024-4835 is a cross-site scripting (XSS) vulnerability in GitLab affecting versions >=15.11.0 <16.10.6, >=16.11.0 <16.11.3, and >=17.0.0 <17.0.1. The vulnerability arises from improper neutralization of input during web page generation, allowing attackers to craft malicious pages that can exfiltrate sensitive user information. This vulnerability has been fixed in GitLab versions 16.10.6, 16.11.3, and 17.0.1.

References

Community reviews

Loading reviews…