CVE-2022-1352Public exploitNetwork attack vector

Restricted issue-title disclosure via Markdown reference rendering

Published May 11, 2022 · Updated Aug 3, 2024

IDOR in GitLab CE/EE 11.0 through 14.8.5, 14.9 through 14.9.3, and 14.10.0 allows remote attackers to read restricted issue titles. The unauthenticated POST /api/v4/markdown route resolves an issue reference supplied through project and text fields, then returns the restricted title in generated link HTML without enforcing the project's issue visibility. Reachability requires a public project with issues limited to project members and a guessed or enumerated issue number; exposure is limited to issue titles.

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

IDOR in GitLab CE/EE 11.0 through 14.8.5, 14.9 through 14.9.3, and 14.10.0 allows remote attackers to read restricted issue titles. The unauthenticated POST /api/v4/markdown route resolves an issue reference supplied through project and text fields, then returns the restricted title in generated link HTML without enforcing the project's issue visibility. Reachability requires a public project with issues limited to project members and a guessed or enumerated issue number; exposure is limited to issue titles.

The record

CVE
CVE-2022-1352
Published
May 11, 2022
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-639, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 11, 2022CVE 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=>=11.0, <14.8.6
  2. Affected versionversion=>=14.10, <14.10.1
  3. Affected versionversion=>=14.9, <14.9.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitLab · GitLabversion=>=11.0, <14.8.6; version=>=14.10, <14.10.1; version=>=14.9, <14.9.4

Published CVSS scores

5.3GitLabCVSS: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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
T1190Exploit Public-Facing Application

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