VulnerabilityPublished 29 Jun 2026Updated 8 Sep 2026

CVE-2026-11379: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

Compare

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

Data as of 12 Nov 2026, 23:24 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 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.1.1, 19.0.3, 18.11.6

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 19.1.1, 19.0.3 or 18.11.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=13.11.0 <18.11.6 >=19.0.0 <19.0.3 >=19.1.0 <19.1.1	Fixed in 18.11.6 19.0.3 19.1.1

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

AI-suggested

Upgrade affected GitLab EE instances to versions 18.11.6, 19.0.3, or 19.1.1 or later where the vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.

Description

GitLab Enterprise Edition versions from 13.11 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain an incorrect authorization vulnerability in DAST site profile management. This flaw could allow a user with Developer role to exfiltrate DAST site profile secrets under certain conditions. The issue has been remediated in versions 18.11.6, 19.0.3, and 19.1.1.

Impact

Users with Developer role could exploit this vulnerability to access and exfiltrate secrets stored in DAST site profiles, potentially exposing sensitive configuration data. This could lead to unauthorized disclosure of confidential information related to dynamic application security testing configurations.

Summary

An authorization vulnerability exists in GitLab EE affecting versions >=13.11 <18.11.6, >=19.0 <19.0.3, and >=19.1 <19.1.1. The flaw allows users with Developer role to bypass intended access controls in DAST site profile management, potentially leading to exfiltration of sensitive DAST site profile secrets. The vulnerability has been fixed in GitLab EE versions 18.11.6, 19.0.3, and 19.1.1.

References

Community reviews

Loading reviews…