CVE-2026-11827 json
Insufficiently Protected Credentials in GitLab
published 4mo ago modified 2mo ago also BIT-gitlab-2026-11827 , EUVD-2026-42404
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user's stored credentials due to improper authorization controls.
Patch / fix
- bitnami gitlab 18.11.7, 19.0.4, 19.1.2
- GitLab GitLab 18.11.7, 19.0.4, 19.1.2
Is CVE-2026-11827 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-11827 updated cvss 4.9
gitlab-ee: GitLab EE: Information disclosure via improper authorization controls
-
Red Hat OpenShift Pipelines openshift-pipelines/pipelines-console-plugin-rhel9, openshift-pipelines/pipelines-console-plugin-pf5-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-console, openshift4/ose-console-rhel9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3720483 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=9.5.0, <18.11.7 >=19.0.0, <19.0.4 >=19.1.0, <19.1.2 |
18.11.7 19.0.4 19.1.2 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
- Technology feeds
References
-
hackerone.com
/reports/3720483
technical-description, exploit, permissions-required, web
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-1-2-released/
vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/602478
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-11827
web
Sources
- CVE List CVE-2026-11827
- NVD CVE-2026-11827
- OSV BIT-gitlab-2026-11827
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.