CVE-2026-1747

CVE-2026-1747 is a medium-severity vulnerability in Gitlab with a CVSS 3.x base score of 4.3. 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-288.

Key facts

Description

GitLab has remediated an issue in GitLab EE affecting all versions from 17.11 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that, under certain conditions, could have allowed Developer-role users with insufficient privileges to make unauthorized modifications to protected Conan packages.

Frequently asked questions

What is CVE-2026-1747?
GitLab has remediated an issue in GitLab EE affecting all versions from 17.11 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that, under certain conditions, could have allowed Developer-role users with insufficient privileges to make unauthorized modifications to protected Conan packages.
How severe is CVE-2026-1747?
CVE-2026-1747 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-1747 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-1747?
CVE-2026-1747 primarily affects Gitlab. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-1747?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-1747 have an EU (EUVD) identifier?
Yes. CVE-2026-1747 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8724.
When was CVE-2026-1747 published?
CVE-2026-1747 was published on 2026-02-25 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-288 vulnerabilities

Browse all CWE-288 vulnerabilities →