CVE-2024-9631

HIGHNVD 7.5
7.5

An issue was discovered in GitLab CE/EE affecting all versions starting from 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, where viewing diffs of MR with conflicts can be slow.

CVSS v3
7.5
EG Score
—
EPSS
—
KEV
Not listed

Published

February 5, 2025

Last Modified

August 6, 2025

References (3)

Vendor Advisories for CVE-2024-9631(1)

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

Frequently asked(4)

What is CVE-2024-9631?
CVE-2024-9631 is a high vulnerability published on February 5, 2025. An issue was discovered in GitLab CE/EE affecting all versions starting from 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, where viewing diffs of MR with conflicts can be slow.
When was CVE-2024-9631 disclosed?
CVE-2024-9631 was first published in the National Vulnerability Database on February 5, 2025, with the most recent update on August 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2024-9631?
CVE-2024-9631 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-9631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-9631, 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-9631

Explore →

Is Your Infrastructure Affected by CVE-2024-9631?

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

Start Free Scan →Browse All CVEs