CVE-2026-12635 json
Reliance on Reverse DNS Resolution for a Security-Critical Action in GitLab
published 2026-06-25 4 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-12635 , EUVD-2026-39168
- cvss
- 0.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to make requests to internal network resources through mirror synchronization due to improper URL validation.
Patch / fix
- bitnami gitlab 18.11.6, 19.0.3, 19.1.1
- GitLab GitLab 18.11.6, 19.0.3, 19.1.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:N |
| NVD | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=8.3.0, <18.11.6 >=19.0.0, <19.0.3 >=19.1.0, <19.1.1 |
18.11.6 19.0.3 19.1.1 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action
- Technology feeds
References
-
docs.gitlab.com
/releases/patches/patch-release-gitlab-19-1-1-released/
release-notes, vendor-advisory, advisory
-
gitlab.com
/gitlab-org/gitlab/-/work_items/594321
broken-link, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-12635
web
Sources
- CVE List CVE-2026-12635
- NVD CVE-2026-12635
- OSV BIT-gitlab-2026-12635
Fencer Vulns 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.