CVE-2024-4835

HIGHNVD 8.08.0—

8.0

A XSS condition exists within GitLab in versions 15.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. By leveraging this condition, an attacker can craft a malicious page to exfiltrate sensitive user information.

CVSS v3: 8.0
EG Score: 8.0(medium)
EPSS: 91.9%
KEV: Not listed

Published

May 23, 2024

Last Modified

December 16, 2024

References (4)

cve@gitlabhttps://gitlab.com/gitlab-org/gitlab/-/issues/461328
cve@gitlabhttps://hackerone.com/reports/2497024
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab/-/issues/461328
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/2497024

Vendor Advisories for CVE-2024-4835(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

patch-release-gitlab-17-0-1-released
GitLab Security
GitLab Patch Release: 17.0.1, 16.11.3, 16.10.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-79Cross-site Scripting (XSS)

Data Freshness Timeline

(refreshed 11× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-24 01:10 UTCEG score recompute
2026-05-24 01:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2024-4835?

CVE-2024-4835 is a high vulnerability published on May 23, 2024. A XSS condition exists within GitLab in versions 15.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. By leveraging this condition, an attacker can craft a malicious page to exfiltrate sensitive user information.

When was CVE-2024-4835 disclosed?

CVE-2024-4835 was first published in the National Vulnerability Database on May 23, 2024, with the most recent update on December 16, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-4835 actively exploited?

CVE-2024-4835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-4835?

CVE-2024-4835 has a CVSS v3 base score of 8.0 (NVD).

How do I remediate CVE-2024-4835?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-4835, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-4835

Explore →

Is Your Infrastructure Affected by CVE-2024-4835?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2024-4835

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2024-4835(1)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)