What is the CVSS score of CVE-2026-1724?

CVE-2026-1724 has a CVSS 3.1 base score of 6.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Gitlab are affected by CVE-2026-1724?

Organizations using GitLab EE affecting all should be aware of notable risk from CVE-2026-1724, a missing authentication vulnerability rated CVSS 6.8.. A patch is available.

Is there a public PoC exploit available for CVE-2026-1724?

Yes, a public proof-of-concept exploit is available for CVE-2026-1724. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-1724?

Within 30 days: Identify affected systems running GitLab EE affecting all and apply vendor patches as part of regular patch cycle. Audit authentication configurations.

Gitlab CVE-2026-1724

EUVD-2026-15484 MEDIUM

Missing Authentication for Critical Function (CWE-306)

2026-03-25 GitLab

GHSA-q22j-w3xw-wf5c

Authentication Bypass Gitlab

6.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.8 MEDIUM

AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

18.9.3,18.8.7,18.10.1

PoC Detected

Mar 26, 2026 - 18:23 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 16:47 euvd

EUVD-2026-15484

Analysis Generated

Mar 25, 2026 - 16:47 vuln.today

CVE Published

Mar 25, 2026 - 16:34 nvd

MEDIUM 6.8

DescriptionCVE.org

GitLab has remediated an issue in GitLab EE affecting all versions from 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to access API tokens of self-hosted AI models due to improper access control.

AnalysisAI

GitLab EE contains an improper access control vulnerability that allows unauthenticated users to retrieve API tokens for self-hosted AI models without authentication. The vulnerability affects GitLab versions 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1, impacting any organization running these versions with AI model integrations. With a CVSS score of 6.8 and publicly available proof-of-concept code, this represents a significant credential exposure risk requiring immediate patching.

Technical ContextAI

The vulnerability stems from a missing authentication check (CWE-306: Missing Authentication for Critical Function) in GitLab EE's AI model integration API endpoints. GitLab's AI features allow organizations to configure connections to self-hosted large language models by storing API tokens within the platform. The affected code path fails to validate user authentication status before exposing these sensitive credentials, allowing unauthenticated attackers over the network to enumerate and extract tokens. This affects GitLab EE as identified by CPE cpe:2.3:a:gitlab:gitlab across multiple minor versions released between Q4 2025 and Q1 2026.

RemediationAI

Immediately upgrade GitLab EE to version 18.8.7 or later for the 18.8 branch, version 18.9.3 or later for the 18.9 branch, or version 18.10.1 or later for the 18.10 branch. Refer to the official GitLab patch release announcement (https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/) and security advisory for detailed upgrade instructions. As an interim measure before patching is possible, rotate all self-hosted AI model API tokens configured within GitLab and audit token access logs through the work item tracker (https://gitlab.com/gitlab-org/gitlab/-/work_items/588334). Additionally, restrict network access to GitLab instances to trusted IP ranges and monitor for any unauthorized API token retrieval attempts in audit logs. Organizations should prioritize patching over workarounds due to the trivial attack vector.