← back to feed
CVE-2026-110264

CVE-2026-110264

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2026-107696 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
GitLab >= 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
fixed in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1
CWE-190 Integer Overflow or Wraparound
ETK-2026-2375Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss10.0cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
49msince last run
1h 29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h51m
0
+4h
+6h
+8h
+10h
+12h

description

GitLab CE and EE releases before the listed fixed versions are affected by an integer overflow during regular-expression compilation. Under certain conditions, an unauthenticated attacker could execute code on the GitLab server.

mitigation

Upgrade GitLab to 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, or 19.5.1, as appropriate for your release line. Restrict unauthenticated access to GitLab until the update is complete.

fixed in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 00:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-22 00:33Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-110264

this entry in the feed

GET /api/v1/feed/CVE-2026-110264

{
  "etk_id": "ETK-2026-2375",
  "cve_id": "CVE-2026-110264",
  "display_id": "CVE-2026-110264",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-107696",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Integer overflow in GitLab regular-expression compilation",
  "summary": "GitLab CE and EE releases before the listed fixed versions are affected by an integer overflow during regular-expression compilation. Under certain conditions, an unauthenticated attacker could execute code on the GitLab server.",
  "mitigation": "Upgrade GitLab to 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, or 19.5.1, as appropriate for your release line. Restrict unauthenticated access to GitLab until the update is complete.",
  "vendor": "GitLab",
  "product": "GitLab",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 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"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "18.11.13",
        "19.0.10",
        "19.1.9",
        "19.2.9",
        "19.3.6",
        "19.4.3",
        "19.5.1"
      ],
      "package_name": "GitLab",
      "purl": null
    }
  ],
  "cwes": [
    190
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 89.07342593333334,
  "t0_at": "2026-10-22T00:33:48.179000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T00:33:48.179000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T00:33:48.179000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110264"
    }
  }
}

published 2026-10-22 00:55Z
last change 2026-10-22 02:57Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.