CVE-2026-5952Network attack vector

Protected metadata overwrite via incorrect authorization

Published Jun 25, 2026 · Updated Jun 25, 2026

Incorrect authorization in GitLab CE/EE allows remote authenticated users to overwrite protected Maven package metadata in protected projects. The Maven Package Registry applies incorrect authorization checks to Developer-role metadata publication, so package protection rules do not block the write; GitLab has not disclosed the code-level locus. Reachability requires Developer access and configured package protection rules, and the bounded consequence is protected metadata modification rather than code execution or disclosure.

CVSS severity4.3
Medium
EPSS probability0.34%
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 authorization in GitLab CE/EE allows remote authenticated users to overwrite protected Maven package metadata in protected projects. The Maven Package Registry applies incorrect authorization checks to Developer-role metadata publication, so package protection rules do not block the write; GitLab has not disclosed the code-level locus. Reachability requires Developer access and configured package protection rules, and the bounded consequence is protected metadata modification rather than code execution or disclosure.

The record

CVE
CVE-2026-5952
Published
Jun 25, 2026
Updated
Jun 25, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-863, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 25, 2026Record 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.11 <18.11.6
  2. Affected versionversion=19.0 <19.0.3
  3. Affected versionversion=19.1 <19.1.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=17.11 <18.11.6; version=19.0 <19.0.3; version=19.1 <19.1.1

Published CVSS scores

4.3GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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

CWE-863Incorrect Authorization
T1565.001Stored Data Manipulation

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