CVE-2026-5816

CVE-2026-5816 is a high-severity vulnerability in Gitlab with a CVSS 3.x base score of 8.0. 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-41.

Key facts

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.4 and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.

Frequently asked questions

What is CVE-2026-5816?
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.4 and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.
How severe is CVE-2026-5816?
CVE-2026-5816 has a CVSS 3.x base score of 8.0, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-5816 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-5816?
CVE-2026-5816 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-5816?
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.
Does CVE-2026-5816 have an EU (EUVD) identifier?
Yes. CVE-2026-5816 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25046.
When was CVE-2026-5816 published?
CVE-2026-5816 was published on 2026-04-22 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-41 vulnerabilities

Browse all CWE-41 vulnerabilities →