CVE-2017-0916

CRITICALNVD 9.89.8—

9.8

Gitlab Community Edition version 10.3 is vulnerable to a lack of input validation in the system_hook_push queue through web hook component resulting in remote code execution.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 62.7%
KEV: Not listed

Published

March 21, 2018

Last Modified

November 21, 2024

References (6)

support@hackeronehttps://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/
support@hackeronehttps://hackerone.com/reports/299473
support@hackeronehttps://www.debian.org/security/2018/dsa-4145
af854a3a-2127-422b-91ae-364da2661108https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/299473
af854a3a-2127-422b-91ae-364da2661108https://www.debian.org/security/2018/dsa-4145

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× 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:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:44 UTCepss_batch
2026-05-23 02:17 UTCEG score recompute
2026-05-23 02:17 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2017-0916?

CVE-2017-0916 is a critical vulnerability published on March 21, 2018. Gitlab Community Edition version 10.3 is vulnerable to a lack of input validation in the systemhookpush queue through web hook component resulting in remote code execution.

When was CVE-2017-0916 disclosed?

CVE-2017-0916 was first published in the National Vulnerability Database on March 21, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-0916 actively exploited?

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

What is the CVSS score of CVE-2017-0916?

CVE-2017-0916 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-0916?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0916, 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-2017-0916

Explore →

Is Your Infrastructure Affected by CVE-2017-0916?

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

Start Free Scan →Browse All CVEs

CVE-2017-0916

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-0916?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)