Protected registry-tag deletion via improper authorization checks
Published May 14, 2026 · Updated May 14, 2026
Authorization bypass in GitLab CE/EE allows remote authenticated users with Developer access to delete protected container registry tags. The container registry tag-deletion path performs improper authorization checks; GitLab has not disclosed the affected function or request handler. Developer-role access to a project with protected container tags is required, and exploitation deletes tags that project policy should preserve.
Summary
What happened
Authorization bypass in GitLab CE/EE allows remote authenticated users with Developer access to delete protected container registry tags. The container registry tag-deletion path performs improper authorization checks; GitLab has not disclosed the affected function or request handler. Developer-role access to a project with protected container tags is required, and exploitation deletes tags that project policy should preserve.
The record
- CVE
- CVE-2026-1338
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=17.10 <18.9.7
- Affected versionversion=18.10 <18.10.6
- Affected versionversion=18.11 <18.11.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- HackerOne Bug Bounty Report #3480620proof of concept · unverified
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