CVE-2025-5069Public exploitNetwork attack vector

Confidential issue disclosure via ambiguous project names

Published Sep 26, 2025 · Updated Sep 26, 2025

Incorrect ownership assignment in GitLab allows remote authenticated users to disclose confidential issues through mistaken transfers. The Move Issue dropdown labels destinations with project names but omits unique slugs, so attacker- and victim-owned projects can appear indistinguishable. Exploitation requires the victim to own the attacker's same-named project and select it while moving a confidential issue, exposing that issue to the attacker.

CVSS severity3.5
Low
EPSS probability0.24%
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

Incorrect ownership assignment in GitLab allows remote authenticated users to disclose confidential issues through mistaken transfers. The Move Issue dropdown labels destinations with project names but omits unique slugs, so attacker- and victim-owned projects can appear indistinguishable. Exploitation requires the victim to own the attacker's same-named project and select it while moving a confidential issue, exposing that issue to the attacker.

The record

CVE
CVE-2025-5069
Published
Sep 26, 2025
Updated
Sep 26, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-708, T1213.003
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 26, 2025CVE publishedPublication date reported by the CVE source.
  2. Sep 26, 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=17.10 <18.2.7
  2. Affected versionversion=18.3 <18.3.3
  3. Affected versionversion=18.4 <18.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=17.10 <18.2.7; version=18.3 <18.3.3; version=18.4 <18.4.1

Published CVSS scores

6.5NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
3.5GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:R/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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-708Incorrect Ownership Assignment
T1213.003Code Repositories

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