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.
- Published
- Oct 22, 2026
- Updated
- Oct 27, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-190
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| gitlab | gitlab | cpe:2.3:a:gitlab:gitlab |
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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | ruby | before 3.3.13-r0 | 3.3.13-r0 |
| Alpine:v3.22 | ruby | before 3.4.12-r0 | 3.4.12-r0 |
| Debian:12 | ruby3.1 | from 0 | — |
| Debian:13 | ruby3.3 | from 0 | — |
Same product
gitlab: all recordsOther 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.KEV100Now
- CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV99Now
- CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV97Now
Published before and after this one in the same product
- ← EarlierCVE-2026-105711Oct 22, 2026 · Use of Cache Containing Sensitive Information in GitLab14Monitor
- ← EarlierCVE-2026-105777Oct 22, 2026 · Insertion of Sensitive Information Into Sent Data in GitLab26Monitor
- Later →CVE-2026-112212Oct 22, 2026 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitLab GitLab | 18.11.13 | Vendor (CNA) |
| GitLab GitLab | 19.0.10 | Vendor (CNA) |
| GitLab GitLab | 19.1.9 | Vendor (CNA) |
| GitLab GitLab | 19.2.9 | Vendor (CNA) |
| GitLab GitLab | 19.3.6 | Vendor (CNA) |
| GitLab GitLab | 19.4.3 | Vendor (CNA) |
| GitLab GitLab | 19.5.1 | Vendor (CNA) |
| azl3 ruby 3.3.5-10 on Azure Linux 3.0 | 3.3.13-0 · Release Notes | Microsoft (MSRC) |
| alpine:ruby | 3.3.13-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:ruby | 3.4.12-r0 · Alpine:v3.24 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-22 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-10-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-24 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-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.
- First PoCsame day
- Published
- Fix recorded+1 d
- TodayNov 1, 2026+11 d
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.
Credits
All researchersFinders, 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 GitLabKEV78This week
- CVE-2026-9357728 days apartInteger Overflow or Wraparound in GitLab39Monitor
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.
- TR-26-1376 · Oct 22, 2026(GitLab CE/EE Güvenlik Bildirimi )
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
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Exploit maturitynone → poc
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.