CVE-2021-22188Public exploitNetwork attack vector

Confidential issue-title disclosure via branch logs

Published Mar 3, 2021 · Updated Aug 3, 2024

Information disclosure in GitLab allows remote attackers to read confidential issue titles through branch logs in affected 13.x releases. The refs branch logs_tree endpoint expands issue references in commit messages into commit_title_html without applying the referenced issue's confidentiality authorization check. Exposure requires a public project with a commit that references a confidential issue; affected releases are 13.0 through 13.6.6, 13.7.0 through 13.7.6, and 13.8.0 through 13.8.3, and no account or project membership is required.

CVSS severity5.3
Medium
EPSS probability1.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in GitLab allows remote attackers to read confidential issue titles through branch logs in affected 13.x releases. The refs branch logs_tree endpoint expands issue references in commit messages into commit_title_html without applying the referenced issue's confidentiality authorization check. Exposure requires a public project with a commit that references a confidential issue; affected releases are 13.0 through 13.6.6, 13.7.0 through 13.7.6, and 13.8.0 through 13.8.3, and no account or project membership is required.

The record

CVE
CVE-2021-22188
Published
Mar 3, 2021
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
Unavailable
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 3, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=13.0, <13.6.7
  2. Affected versionversion=>=13.7, <13.7.7
  3. Affected versionversion=>=13.8, <13.8.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitLab · GitLabversion=>=13.0, <13.6.7; version=>=13.7, <13.7.7; version=>=13.8, <13.8.4

Published CVSS scores

5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N
5.3GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo