CVE-2026-85706: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

Published Sep 11, 2026
·
Updated

GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.

Other sources

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 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.

— MITRE

Affected Software

11 affected components
GitLab Community Edition and Enterprise Edition
GitLab GitLab>=18.7.0<18.11.12
GitLab GitLab>=18.7.0<18.11.12
GitLab GitLab>=19.0.0<19.0.9
GitLab GitLab>=19.0.0<19.0.9
GitLab GitLab>=19.1.0<19.1.8
GitLab GitLab>=19.1.0<19.1.8
GitLab GitLab>=19.2.0<19.2.6
GitLab GitLab>=19.2.0<19.2.6
GitLab GitLab>=19.3.0<19.3.2
GitLab GitLab>=19.3.0<19.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitLab Community Edition to a version that resolves this vulnerability.

    Fixed in 18.11.12
  2. Upgrade

    Upgrade GitLab Enterprise Edition to a version that resolves this vulnerability.

    Fixed in 18.11.12
  3. Upgrade

    Upgrade GitLab Community Edition to a version that resolves this vulnerability.

    Fixed in 19.0.9
  4. Upgrade

    Upgrade GitLab Enterprise Edition to a version that resolves this vulnerability.

    Fixed in 19.0.9
  5. Upgrade

    Upgrade GitLab Community Edition to a version that resolves this vulnerability.

    Fixed in 19.1.8
  6. Upgrade

    Upgrade GitLab Enterprise Edition to a version that resolves this vulnerability.

    Fixed in 19.1.8
  7. Upgrade

    Upgrade GitLab Community Edition to a version that resolves this vulnerability.

    Fixed in 19.2.6
  8. Upgrade

    Upgrade GitLab Enterprise Edition to a version that resolves this vulnerability.

    Fixed in 19.2.6
  9. Upgrade

    Upgrade GitLab Community Edition to a version that resolves this vulnerability.

    Fixed in 19.3.2
  10. Upgrade

    Upgrade GitLab Enterprise Edition to a version that resolves this vulnerability.

    Fixed in 19.3.2

Event History

Sep 11, 2026
Kev Listed
via CISA·12:00 AM
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Sep 12, 2026
CVE Published
via MITRE·02:46 AM
Data Sourced
via MITRE·02:46 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·03:16 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Is exploitation in the wild known?

Yes. This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog as of 2026-09-11.

2

Does an attacker need an account to exploit this issue?

No. The issue is described as exploitable by an unauthenticated user.

3

Is vendor patch information available?

Yes. A GitLab patch-release reference is provided for GitLab 19.3.2, but the supplied data does not identify the full affected or fixed version ranges.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203