CVE-2025-10868: Business Logic Errors in GitLab

Published Sep 25, 2025
·
Updated

An issue has been discovered in GitLab CE/EE affecting all versions from 17.4 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1 where certain string conversion methods exhibit performance degradation with large inputs.

Other sources

GitLab has remediated an issue that could have allowed an authenticated user to cause performance degradation, potentially leading to a Denial of Service condition with certain string conversion methods.

GitLab

Affected Software

8 affected componentsFixes available
GitLab GitLab CE/EE>=17.4, <18.2.7, >=18.3, <18.3.3, >=18.4, <18.4.1
GitLab GitLab>=17.4.0<18.2.7
GitLab GitLab>=17.4.0<18.2.7
GitLab GitLab>=18.3.0<18.3.3
GitLab GitLab>=18.3.0<18.3.3
GitLab GitLab=18.4.0
GitLab GitLab=18.4.0
GitLab GitLab>=17.4<18.2.7, >=18.3<18.3.3, >=18.4<18.4.1
18.2.718.3.318.4.1

Remediation

Information

Upgrade to version 18.2.7, 18.3.3 or 18.4.1 or above.

Event History

Sep 26, 2025
CVE Published
via MITRE·09:10 AM
Data Sourced
via MITRE·09:10 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·08:55 AM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-10868?

CVE-2025-10868 has been classified as a medium-severity vulnerability due to performance degradation issues.

2

What versions of GitLab are affected by CVE-2025-10868?

CVE-2025-10868 affects GitLab CE/EE versions from 17.4 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1.

3

How do I fix CVE-2025-10868?

To resolve CVE-2025-10868, upgrade GitLab CE/EE to version 18.2.7, 18.3.3, or 18.4.1 or later.

4

What is the impact of CVE-2025-10868?

The impact of CVE-2025-10868 is mainly performance degradation when processing large inputs in certain string conversion methods.

5

Is there a workaround for CVE-2025-10868?

There is no documented workaround for CVE-2025-10868; updating to a patched version is recommended.

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