← console
voxell vciy

CVE-2024-3958: Improper Control of Generation of Code ('Code Injection') in GitLab

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: 17.0.6; 17.1.4; 17.2.2 CVE record
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

An issue has been discovered in GitLab CE/EE affecting all versions before 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2. An issue was found that allows someone to abuse a discrepancy between the Web application display and the git command line interface to social engineer victims into cloning non-trusted code.

weakness
CWE-94: Improper Control of Generation of Code ('Code Injection')
affected
GitLab
published ranges
gitlab < 17.0.6; gitlab >= 17.1.0 < 17.1.4; gitlab >= 17.2.0 < 17.2.2
fixed in
17.0.6; 17.1.4; 17.2.2
fixed by package (from OSV advisories)
gitlab (Bitnami): 17.0.6; 17.1.4; 17.2.2 BIT-gitlab-2024-3958
severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
assigned by
GitLab
published
2024-08-08

check us gitlab.com hackerone.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
13 Aug 20240.00043
30 Aug 20240.00047
17 Mar 20250.00049scoring model v2025.03.14
19 Mar 20250.00053
25 Apr 20260.00111
8 May 20260.00102
15 Jun 20260.00301scoring model v2026.06.15
17 Jul 20260.0032

21 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-07-17 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 17.0.6; 17.1.4; 17.2.2. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-3958', '2026-10-31T23:59:59.999999Z', now());