CVE-2023-3932

CVE-2023-3932 is a high-severity vulnerability in Gitlab with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-286.

Key facts

Description

An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies.

Frequently asked questions

What is CVE-2023-3932?
An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies.
How severe is CVE-2023-3932?
CVE-2023-3932 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2023-3932 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-3932?
CVE-2023-3932 affects Gitlab. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-3932?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2023-3932 published?
CVE-2023-3932 was published on 2023-08-03 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-286 vulnerabilities

Browse all CWE-286 vulnerabilities →