CVE-2022-2761Network attack vector

Private resource-name disclosure via Jira GFM references

Published Nov 9, 2022 · Updated May 1, 2025

Information exposure in GitLab 15.5.1 and earlier allows remote attackers to disclose private resource names via Jira GFM references. The JiraGfmPipeline renders arbitrary GitLab Flavored Markdown references in Jira issue descriptions without redacting references to private or confidential issues, merge requests, and other resources. Exploitation requires a configured Jira integration and an account able to create or view the Jira issue; the consequence is disclosure of resource names without data modification or service interruption.

CVSS severity4.3
Medium
EPSS probability0.71%
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 exposure in GitLab 15.5.1 and earlier allows remote attackers to disclose private resource names via Jira GFM references. The JiraGfmPipeline renders arbitrary GitLab Flavored Markdown references in Jira issue descriptions without redacting references to private or confidential issues, merge requests, and other resources. Exploitation requires a configured Jira integration and an account able to create or view the Jira issue; the consequence is disclosure of resource names without data modification or service interruption.

The record

CVE
CVE-2022-2761
Published
Nov 9, 2022
Updated
May 1, 2025
Vendor
GitLab
Product
GitLab
Classifications
Unavailable
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 9, 2022CVE publishedPublication date reported by the CVE source.
  2. May 1, 2025Record 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.9, <15.3.5
  2. Affected versionversion=>=15.4, <15.4.4
  3. Affected versionversion=>=15.5, <15.5.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=13.9, <15.3.5; version=>=15.4, <15.4.4; version=>=15.5, <15.5.2

Published CVSS scores

5.3NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.3GitLabCVSS:3.1/AV:N/AC:L/PR:L/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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

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