CVE-2026-1732 Improper Removal of Sensitive Information Before Storage or Transfer in GitLab
An authenticated user can disclose confidential issue titles due to improper filtering, requiring an upgrade to GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-1732?
CVE-2026-1732 is a medium-severity vulnerability in Gitlab Gitlab, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.6 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to disclose confidential issue titles due to improper filtering under certain circumstances.
Weakness: CWE-212
Which versions are affected by CVE-2026-1732?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.6.0 | 18.7.6, 18.8.6, 18.9.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2026-1732?
Upgrade gitlab to a fixed version for your release line: 18.7.6, 18.8.6 or 18.9.2.
Is CVE-2026-1732 being exploited?
There is no known exploitation of CVE-2026-1732 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2026-1732, GHSA-gcgf-w628-jq5c, UBUNTU-CVE-2026-1732.