CVE-2024-13041Public exploitNetwork attack vector

Internal project access via SAML status override

Published Jan 9, 2025 · Updated Jan 9, 2025

Authorization flaw in GitLab 16.4 through 17.5.4, 17.6 through 17.6.2, and 17.7.0 allows remote authenticated users to access internal projects. GitLab::Auth::Saml::User#find_user applies SAML external-group membership after the OmniAuth external-provider setting, overwriting a true external attribute when a new user is outside the configured external groups. Exploitation requires instance-wide SAML with both settings and a newly created SAML account; the account gains internal visibility but no administrator role.

CVSS severity4.3
Medium
EPSS probability0.28%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization flaw in GitLab 16.4 through 17.5.4, 17.6 through 17.6.2, and 17.7.0 allows remote authenticated users to access internal projects. GitLab::Auth::Saml::User#find_user applies SAML external-group membership after the OmniAuth external-provider setting, overwriting a true external attribute when a new user is outside the configured external groups. Exploitation requires instance-wide SAML with both settings and a newly created SAML account; the account gains internal visibility but no administrator role.

The record

CVE
CVE-2024-13041
Published
Jan 9, 2025
Updated
Jan 9, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-286, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 9, 2025CVE publishedPublication date reported by the CVE source.
  2. Jan 9, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=16.4 <17.5.5
  2. Affected versionversion=17.6 <17.6.3
  3. Affected versionversion=17.7 <17.7.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=16.4 <17.5.5; version=17.6 <17.6.3; version=17.7 <17.7.1

Published CVSS scores

5.4NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.3GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-286Incorrect User Management
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo