GitLab 5.0 before 5.4.2, Community Edition before 6.2.4, Enterprise Edition before 6.2.1 and gitlab-shell before 1.7.8 allows remote attack…

published 2014-05-12 12y ago modified 2026-06-16 4mo ago also EUVD-2013-4439

cvss: 6.8; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.1%; EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits: 0; none known

GitLab 5.0 before 5.4.2, Community Edition before 6.2.4, Enterprise Edition before 6.2.1 and gitlab-shell before 1.7.8 allows remote attackers to execute arbitrary code via a crafted change using SSH.

Patch / fix

links 1

gitlab.com/2013/11/14/multiple-critical-vulnerabilities-in-gitlab/ advisory

Is CVE-2013-4581 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.06% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-94 Improper Control of Generation of Code

Technology feeds

GitLab rss critical rss

References

gitlab.com /2013/11/14/multiple-critical-vulnerabilities-in-gitlab/
patch, vendor-advisory
openwall.com /lists/oss-security/2013/11/15/4
mailing-list

Sources

CVE List CVE-2013-4581
NVD CVE-2013-4581

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.