Database/Control plane, storage & DevOps
GitLab: crafted file names can hide changes from reviewers in merge request diffs
Impact
GitLab mishandles certain file names when it renders merge request diffs. An authenticated author can make some changes invisible to reviewers, so a reviewer can approve a merge request without seeing everything it changes. Where merge request review is the control in front of infrastructure-as-code, cluster manifests or GitOps repositories, this weakens it: unreviewed content can reach production through an approved merge. Affects 19.0 before 19.3.9, 19.4 before 19.4.8 and 19.5 before 19.5.6.
Who can reach it
An authenticated GitLab user who can open a merge request. A reviewer has to view and approve it (user interaction).
What to do
Upgrade to 19.3.9, 19.4.8 or 19.5.6 per the GitLab 19.5.6 patch release. This is a package upgrade and a service restart on a self-managed instance. For sensitive repositories, consider re-checking recently merged changes with a local git diff instead of the web UI.
References
Related entries
- GitLab: repository import can be used to make requests to internal network services (SSRF)CVE-2026-126141 · GitLab CE/EE (repository import, destination address validation)Low
- GitLab EE: reporter-role author of a merge request can reset its approval rulesCVE-2026-7487 · GitLab EE (merge request approval rules, authorization check)Low
- Jenkins: Overall/Manage holders can change Appearance configuration reserved for administratorsCVE-2026-84653 · Jenkins core (Appearance configuration page permission checks)Low
- IBM Spectrum Scale Local Read Only Cache (LROC): With LROC enabled, a read of one file can silently return the contentsCVE-2018-1993 · IBM Spectrum Scale Local Read Only Cache (LROC)Low
- DDR3 and DDR4 DRAM, including ECC modules; tracked by Intel as a partial-physical-address disclosure issue: TurnsCVE-2019-0174 · DDR3 and DDR4 DRAM, including ECC modules; tracked by Intel as a partial-physical-address disclosure issueLow
- IBM Spectrum Scale file audit logging: A local user touches files without the access being recorded, so the audit trailCVE-2021-29671 · IBM Spectrum Scale file audit loggingLow
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.