Is CVE-2026-11827 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-11827 being exploited in the wild.

How severe is CVE-2026-11827?

Medium severity, with a CVSS score of 4.9, published 8 July 2026.

Which products and versions are affected?

GitLab EE 9.5 before 18.11.7, 19.0 before 19.0.4, 19.1 before 19.1.2.

Is there a fix for CVE-2026-11827?

A patch was published on 2026-07-08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-11827 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-11827?

Check whether you run GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11827: GitLab GitLab EE credential disclosure in repository mirroring

CVE-2026-11827 · Severity: medium · CVSS 4.9 · Published 2026-07-08

GitLab Enterprise Edition (EE), a platform used for software development and version control, contained a security flaw in its repository mirroring feature. This vulnerability could allow a user with high-level 'Maintainer' permissions to improperly access the stored credentials of another user. If exploited, this could lead to unauthorized access to external systems or repositories linked to the affected GitLab instance.

Technologies: GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-11827 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-11827 being exploited in the wild.
How severe is CVE-2026-11827?: Medium severity, with a CVSS score of 4.9, published 8 July 2026.
Which products and versions are affected?: GitLab EE 9.5 before 18.11.7, 19.0 before 19.0.4, 19.1 before 19.1.2.
Is there a fix for CVE-2026-11827?: A patch was published on 2026-07-08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-11827 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-11827?: Check whether you run GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An Insufficiently Protected Credentials vulnerability (CWE-522) exists in GitLab EE's repository mirroring component. The flaw stems from improper authorization controls that fail to adequately restrict access to stored credentials under specific conditions. An authenticated attacker with 'Maintainer' role permissions can exploit this over the network to retrieve credentials belonging to other users. The issue affects GitLab EE versions 9.5 through 18.11.6, 19.0.x before 19.0.4, and 19.1.x before 19.1.2. GitLab has released patches in versions 18.11.7, 19.0.4, and 19.1.2 to remediate this behavior.

Affected products

GitLab GitLab EE 9.5 before 18.11.7, 19.0 before 19.0.4, 19.1 before 19.1.2

Timeline

2026-07-08: advisory
2026-07-08: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.