CVE-2026-6267: gitlab — Fix

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling.

Is your site exposed to CVE-2026-6267?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

8.5

HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS — Exploit Prediction

0.0033

Probability of exploitation

0.26%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-201 CWE-201

Affected Products

Vendor	Product	Versions
gitlab	gitlab	10.1.0 — 19.0.5
gitlab	gitlab	10.1.0 — 19.0.5
gitlab	gitlab	19.1.0 — 19.1.3
gitlab	gitlab	19.1.0 — 19.1.3
gitlab	gitlab	All
gitlab	gitlab	All

References

Advisories & Patches

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/

Other References

https://gitlab.com/gitlab-org/gitlab/-/work_items/596606 https://hackerone.com/reports/3658324

Frequently Asked Questions

What is CVE-2026-6267? +

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling. It has a CVSS v3.1 base score of 8.5 (HIGH).

How severe is CVE-2026-6267? +

CVE-2026-6267 has a CVSS v3.1 score of 8.5 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0033, placing it in the 0th percentile for exploitation probability.

What products are affected by CVE-2026-6267? +

CVE-2026-6267 affects products from gitlab, specifically: gitlab. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2026-6267? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-27868

An attacker with access via network to the Regesta Smart HD-PLC of the provider Teldat (in this case, NO registration …

CVE-2025-24858

Develocity (formerly Gradle Enterprise) before 2024.3.1 allows an attacker who has network access to a Develocity server to obtain the …

CVE-2025-48045

An unauthenticated HTTP GET request to the /client.php endpoint will disclose the default administrator user credentials.

CVE-2024-7205

When the device is shared, the homepage module are before 2.19.0 in eWeLink Cloud Service allows Secondary user to take …

CVE-2025-8862

YugabyteDB has been collecting diagnostics information from YugabyteDB servers, which may include sensitive gflag configurations. To mitigate this, we recommend …

CVE-2025-64502

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. The MongoDB …

CVE-2026-6267