CVE-2026-3607Network attack vector

Developer-level package protection bypass via post-access authorization

Published May 14, 2026 · Updated May 14, 2026

Improper access control in affected GitLab CE/EE releases allows remote authenticated users to bypass package protection rules. GitLab maps the flaw to CWE-1280, indicating that authorization occurs only after a protected package asset is accessed, but the affected code path and operation remain undisclosed. Developer-role access and a configured protection rule are required, and the bypass permits a package-registry action that the rule should block.

CVSS severity4.3
Medium
EPSS probability0.23%
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

Improper access control in affected GitLab CE/EE releases allows remote authenticated users to bypass package protection rules. GitLab maps the flaw to CWE-1280, indicating that authorization occurs only after a protected package asset is accessed, but the affected code path and operation remain undisclosed. Developer-role access and a configured protection rule are required, and the bypass permits a package-registry action that the rule should block.

The record

CVE
CVE-2026-3607
Published
May 14, 2026
Updated
May 14, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-1280, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 14, 2026CVE publishedPublication date reported by the CVE source.
  2. May 14, 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=18.10 <18.10.6
  2. Affected versionversion=18.11 <18.11.3
  3. Affected versionversion=18.3 <18.9.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=18.10 <18.10.6; version=18.11 <18.11.3; version=18.3 <18.9.7

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-1280Access Control Check Implemented After Asset is Accessed
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