Skip to main content
VulnerabilityPublished Updated

CVE-2026-4879: GitLab · Missing Authorization

Affects gitlabSource GCVE Database

0
Compare

Not known to be exploited · fixed in 19.2.2 : update gitlab when convenient.

Data as of 17 Nov 2026, 20:25 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 19.2.2, 19.1.4, 19.0.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade gitlab to 19.2.2, 19.1.4 or 19.0.6.

Affected software

ProductAffectedFixed in
Bitnamigitlabpkg:bitnami/gitlabOther threatsAffected
  • >=16.0.0 <19.0.6
  • >=19.1.0 <19.1.4
  • >=19.2.0 <19.2.2
Fixed in
  • 19.0.6
  • 19.1.4
  • 19.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

GitLab has released official patches that remediate this vulnerability in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab EE instances to these versions or later to resolve the issue. Since this is not a cloud service, remediation is the responsibility of the user. No additional mitigations are specified.

Description

A missing authorization vulnerability in GitLab EE versions from 16.0 up to but not including 19.0.6, 19.1 up to 19.1.4, and 19.2 up to 19.2.2 could allow an authenticated user with developer-role permissions to view external status check configurations that should be restricted to higher-privileged roles. This issue affects a merge request API endpoint and has been remediated by GitLab.

References

Community reviews

Loading reviews…