CVE-2026-0934Patch(gitlab / gitlab)

LOWCVSS 3.8 · LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch gitlab gitlab systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

GitLab has remediated an issue in GitLab EE affecting all versions from 17.9 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with custom role permissions to view, create, or delete protected environment configurations despite CI/CD visibility being disabled for the project.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-863

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • gitlab

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
gitlab

1 version affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-25: 1Patch / Workaround · 2026-06-25: 106-25
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Clone Systems@CloneSystemsInc
    Patch

    GitLab EE has patched CVE-2026-0934, an incorrect authorization vulnerability that could allow unauthorized management of protected environments. Protected environments are designed to control who can deploy to sensitive areas like production, staging, or critical application workflows. When authorization checks fail, the risk is not just access. It is control over the systems that keep deployments safe. Organizations running affected GitLab EE versions should upgrade to the fixed releases immediately, review custom role permissions, and monitor protected environment settings for unexpected changes. Access control issues can be quiet, but the impact can be loud. Review who has deployment privileges before someone else does it for you. #GitLab #CVE20260934 #VulnerabilityManagement #AccessControl #DevSecOps #PatchManagement #ApplicationSecurity #CloudSecurity #Cybersecurity #CyberRisk

    Post summary

    The post informs that GitLab EE has patched CVE‑2026‑0934, an incorrect authorization vulnerability, and advises immediately upgrading, reviewing role permissions, and watching protected environment settings.

    0001093
    259 followersView on X
CPE platform detail2 entries

2 of 2 entries

PartVendorProductVersionTarget SWTarget HW
Appgitlabgitlab---
Appgitlabgitlab19.1.0--

Explore more