CVE-2026-110264: Integer Overflow or Wraparound in GitLab

Published Oct 22, 2026
·
Updated

An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression.

Other sources

Integer Overflow or Wraparound in GitLab

— Microsoft

Affected Software

29 affected componentsFixes available
GitLab GitLab CE/EE>=7.0<18.11.13, >=19.0<19.0.10, >=19.1<19.1.9, >=19.2<19.2.9, >=19.3<19.3.6, >=19.4<19.4.3, >=19.5<19.5.1
All of the following
azurelinux/ruby<3.3.13-0
3.3.13-0
Microsoft Azure Linux=3.0
bitnami/gitlab>=7.0.0<18.11.13
18.11.13
bitnami/gitlab>=19.0.0<19.0.10
19.0.10
bitnami/gitlab>=19.1.0<19.1.9
19.1.9
bitnami/gitlab>=19.2.0<19.2.9
19.2.9
bitnami/gitlab>=19.3.0<19.3.6
19.3.6
bitnami/gitlab>=19.4.0<19.4.3
19.4.3
bitnami/gitlab>=19.5.0<19.5.1
19.5.1
GitLab GitLab>=7.0.0<18.11.13
GitLab GitLab>=7.0.0<18.11.13
GitLab GitLab>=19.0.0<19.0.10
GitLab GitLab>=19.0.0<19.0.10
GitLab GitLab>=19.1.0<19.1.9
GitLab GitLab>=19.1.0<19.1.9
GitLab GitLab>=19.2.0<19.2.9
GitLab GitLab>=19.2.0<19.2.9
GitLab GitLab>=19.3.0<19.3.6
GitLab GitLab>=19.3.0<19.3.6
GitLab GitLab>=19.4.0<19.4.3
GitLab GitLab>=19.4.0<19.4.3
GitLab GitLab=19.5.0
GitLab GitLab=19.5.0
debian/ruby3.1*
debian/ruby3.3<3.3.13-0+deb13u1
3.3.13-0+deb13u1
debian/ruby3.3*
debian/ruby3.1<=3.1.2-7+deb12u1
debian/ruby3.3<=3.3.8-2, <=3.3.8-2.2
3.3.13-0+deb13u1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade azurelinux/ruby to a version that resolves this vulnerability.

    Fixed in 3.3.13-0
  2. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 18.11.13
  3. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.0.10
  4. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.1.9
  5. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.2.9
  6. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.3.6
  7. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.4.3
  8. Upgrade

    Upgrade bitnami/gitlab to a version that resolves this vulnerability.

    Fixed in 19.5.1
  9. Upgrade

    Upgrade debian/ruby3.3 to a version that resolves this vulnerability.

    Fixed in 3.3.13-0+deb13u1
  10. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 18.11.13
  11. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.0.10
  12. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.1.9
  13. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.2.9
  14. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.3.6
  15. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.4.3
  16. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 19.5.1

Event History

Oct 22, 2026
CVE Published
via MITRE·12:33 AM
Data Sourced
via MITRE·12:33 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via OSV·12:33 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·12:53 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeaknessAffected Software
Exploit Published
via GitHub·04:10 PM
News Published
via The Register·05:36 PM
Oct 25, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:02 AM
Affected Software
Oct 29, 2026
Advisory Published
via OSV·09:10 AM
Nov 5, 2026
News Published
via ZDNet·02:00 PM
Nov 7, 2026
Data Sourced
via OSV·07:00 PM
Affected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which GitLab instances are exposed?

GitLab CE/EE versions from 7.0 up to, but not including, 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, or 19.5.1 are affected. The issue applies when the conditions needed to compile a specially crafted regular expression are present.

2

Does exploitation require an account or user interaction?

No. The vulnerability is remotely exploitable with low attack complexity and requires neither authentication nor user interaction.

3

What could an attacker achieve?

Under certain conditions, an unauthenticated attacker could execute arbitrary code on the GitLab server. The reported impact includes high confidentiality, integrity, and availability consequences.

4

What is the remediation?

Upgrade GitLab CE/EE to 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1, or a later version, as appropriate for the deployment's release line.

Company

Resources

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