How severe is CVE-2020-13327?

CVE-2020-13327 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2020-13327 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-13327?

CVE-2020-13327 affects Gitlab Runner. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-13327?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-13327 published?

CVE-2020-13327 was published on 2020-10-22 and last updated on 2026-06-17.

CVE-2020-13327

CVE-2020-13327 is a medium-severity vulnerability in Gitlab Runner with a CVSS 3.x base score of 6.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 6.0)
CVSS v2: 6.0
EPSS exploit prediction: 1% (49th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gitlab Runner
Published: 2020-10-22
Last modified: 2026-06-17

Description

An issue has been discovered in GitLab Runner affecting all versions starting from 13.4.0 before 13.4.2, all versions starting from 13.3.0 before 13.3.7, all versions starting from 13.2.0 before 13.2.10. Insecure Runner Configuration in Kubernetes Environments

Frequently asked questions

What is CVE-2020-13327?: An issue has been discovered in GitLab Runner affecting all versions starting from 13.4.0 before 13.4.2, all versions starting from 13.3.0 before 13.3.7, all versions starting from 13.2.0 before 13.2.10. Insecure Runner Configuration in Kubernetes Environments
How severe is CVE-2020-13327?: CVE-2020-13327 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2020-13327 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-13327?: CVE-2020-13327 affects Gitlab Runner. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-13327?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-13327 published?: CVE-2020-13327 was published on 2020-10-22 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gitlab:runner:*:*:*:*:*:*:*:*

More vulnerabilities in Gitlab Runner

CVE-2020-13295 — Medium (CVSS 5.4): For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is…
CVE-2022-2251 — Medium (CVSS 4.8): Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4,…

All CVEs affecting Gitlab Runner →