Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Improper authentication in GitLab Virtual Registries credential handling

IdentifiersCVE-2026-6515CWE-287

GitLab CE/EE contains a vulnerability affecting all versions from 18.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. Under certain conditions, a user could use invalidated or incorrectly scoped credentials to access Virtual Registries. Based on the available description, the flaw appears to stem from improper enforcement of credential validity and/or scope checks during access to Virtual Registries, allowing credentials that should no longer be accepted, or that should not authorize the requested registry access, to be treated as valid.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could allow unauthorized access to GitLab Virtual Registries using credentials that were invalidated or not properly scoped for the requested resource. This may permit access beyond intended authorization boundaries and could expose registry content or related resources to users who should no longer have access or never had the correct scope.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting access to Virtual Registries to only necessary users and networks, rotating potentially affected credentials, revoking stale tokens, and monitoring for anomalous registry access that may indicate use of invalidated or over-scoped credentials. Additional compensating controls may include temporarily disabling affected workflows or tightening token scope assignments where operationally feasible.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.9.6 or later for the 18.9 series, 18.10.4 or later for the 18.10 series, or 18.11.1 or later for the 18.11 series. Organizations should also review credential lifecycle handling and validate that revoked, expired, or scope-limited credentials are no longer usable for Virtual Registry access after patching.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.