Skip to content
Noroxi
NVD / CVE Program· CNA GitLab

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

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: GitLab GitLab 18.11.13, 19.0.10, 19.1.9; azl3 ruby 3.3.5-10 on Azure Linux 3.0 3.3.13-0.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to GitLab GitLab 18.11.13, 19.0.10, 19.1.9; azl3 ruby 3.3.5-10 on Azure Linux 3.0 3.3.13-0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 10.0 · v3.1—Proof of concept Fix available
Published
Oct 22, 2026
Updated
Oct 27, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitLab
10.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-110264

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gitlabgitlab

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gitlab gitlab7.0.0 and later · before 18.11.13
  • gitlab gitlab19.0.0 and later · before 19.0.10
  • gitlab gitlab19.1.0 and later · before 19.1.9
  • gitlab gitlab19.2.0 and later · before 19.2.9
  • gitlab gitlab19.3.0 and later · before 19.3.6
  • gitlab gitlab19.4.0 and later · before 19.4.3
  • gitlab gitlab19.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

  • GitLab GitLab

    • 7.0 and later · before 18.11.13affected · semver
    • 19.0 and later · before 19.0.10affected · semver
    • 19.1 and later · before 19.1.9affected · semver
    • 19.2 and later · before 19.2.9affected · semver
    • 19.3 and later · before 19.3.6affected · semver
    • 19.4 and later · before 19.4.3affected · semver
    • 19.5 and later · before 19.5.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.21rubybefore 3.3.13-r03.3.13-r0
Alpine:v3.22rubybefore 3.4.12-r03.4.12-r0
Debian:12ruby3.1from 0—
Debian:13ruby3.3from 0—

Other highest-scoring records for the same primary product.

  • CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
    100Now
  • CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
    99Now
  • CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
    97Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-105711Oct 22, 2026 · Use of Cache Containing Sensitive Information in GitLab
    14Monitor
  • ← EarlierCVE-2026-105777Oct 22, 2026 · Insertion of Sensitive Information Into Sent Data in GitLab
    26Monitor
  • Later →CVE-2026-112212Oct 22, 2026 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
GitLab GitLab18.11.13Vendor (CNA)
GitLab GitLab19.0.10Vendor (CNA)
GitLab GitLab19.1.9Vendor (CNA)
GitLab GitLab19.2.9Vendor (CNA)
GitLab GitLab19.3.6Vendor (CNA)
GitLab GitLab19.4.3Vendor (CNA)
GitLab GitLab19.5.1Vendor (CNA)
azl3 ruby 3.3.5-10 on Azure Linux 3.03.3.13-0 · Release NotesMicrosoft (MSRC)
alpine:ruby3.3.13-r0 · Alpine:v3.21Package registry (OSV)
alpine:ruby3.4.12-r0 · Alpine:v3.24Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-10-22
Proof-of-concept repository on GitHubstars:02026-10-22
Proof-of-concept repository on GitHubstars:22026-10-22
Proof-of-concept repository on GitHubstars:02026-10-22
Proof-of-concept repository on GitHubstars:02026-10-23
Proof-of-concept repository on GitHubstars:02026-10-23
Proof-of-concept repository on GitHubstars:02026-10-23
Proof-of-concept repository on GitHubstars:02026-10-23
Proof-of-concept repository on GitHubstars:02026-10-23
Proof-of-concept repository on GitHubstars:02026-10-24
Proof-of-concept repository on GitHubstars:02026-10-24

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoCsame day
  2. Published
  3. Fix recorded+1 d
  4. TodayNov 1, 2026+11 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-972299 days apartInteger Overflow or Wraparound in GitLabKEV
    78This week
  • CVE-2026-9357728 days apartInteger Overflow or Wraparound in GitLab
    39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Exploit maturitynone → poc
  2. Fix✗ → ✓
  3. SSVC exploitation— → none
  4. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records