GitLab up to 19.1.7/19.2.5/19.3.1 Repository Commits API missing authentication

Summaryinfo

A vulnerability categorized as problematic has been discovered in GitLab up to 19.1.7/19.2.5/19.3.1. This affects an unknown function of the component Repository Commits API. The manipulation results in missing authentication. This vulnerability is identified as CVE-2026-85706. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab up to 19.1.7/19.2.5/19.3.1. It has been classified as problematic. Affected is an unknown functionality of the component Repository Commits API. The manipulation with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality. CVE summarizes:

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.

The advisory is available at gitlab.com. This vulnerability is traded as CVE-2026-85706 since 09/04/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.

This issue was added on 09/11/2026 to the CISA Known Exploited Vulnerabilities Catalog with a due date of 09/14/2026:

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BO

Upgrading to version 19.1.8, 19.2.6 or 19.3.2 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Bug Tracking Software

Name

• GitLab

Version

• 19.1.0
• 19.1.1
• 19.1.2
• 19.1.3
• 19.1.4
• 19.1.5
• 19.1.6
• 19.1.7
• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.3.0
• 19.3.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion