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

Incorrect Authorization in GitLab EE DAST Site Profile Management

IdentifiersCVE-2026-11379CWE-863

CVE-2026-11379 is an incorrect authorization vulnerability in GitLab Enterprise Edition affecting all versions from 13.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. The flaw exists in DAST site profile management, where authorization checks are insufficient, allowing a user with the Developer role to access and exfiltrate DAST site profile secrets under certain conditions. The issue is described by GitLab as impacting DAST scanner and site profile management and results in exposure of secrets associated with DAST site profiles.

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 allows a Developer-role user to obtain sensitive DAST site profile secrets that should not be accessible to that role. This can result in disclosure of credentials, tokens, or other secret material stored in the DAST site profile configuration, potentially enabling further access to scanned applications, related environments, or downstream systems depending on how those secrets are used.

Mitigation

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

If immediate patching is not possible, restrict Developer-role access to projects and groups that use DAST site profiles containing sensitive secrets, minimize the number of users permitted to manage or interact with DAST configuration, review and rotate any secrets stored in DAST site profiles that may have been exposed, and monitor for unauthorized access or export of DAST-related configuration data. These are risk-reduction measures only; the primary mitigation is upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release: 18.11.6, 19.0.3, 19.1.1, or later. GitLab stated that self-managed installations should upgrade immediately. GitLab.com was already patched at the time of disclosure, and GitLab Dedicated customers were reported as requiring no action.
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.

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 activity2

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