CVE-2026-97229

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

GHSA-9hj5-r43h-h3xg ↗EUVD-2026-98214 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+8h34mkevAttacks confirmed in the real world.
GitLab >= 19.2, < 19.2.8; >= 19.3, < 19.3.5; >= 19.4, < 19.4.2
fixed in 19.2.8, 19.3.5, 19.4.2
CWE-190 Integer Overflow or Wraparound
ETK-2026-1451Zero's internal tracking ID, independent of the CVE number., permanent identifier
7d 10h 59msince last run
1h 24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hpublic poc+8h34mwaiting for further signals+25h34m
0
+2h
+4h
+6h
+8h

description

GitLab CE/EE versions before 19.2.8, 19.3.5, and 19.4.2 in their respective release lines are affected. If a CI/CD configuration containing a malicious regular expression is processed under the relevant conditions, an unauthenticated remote attacker may be able to run code on the GitLab server.

mitigation

Upgrade GitLab CE/EE to 19.2.8, 19.3.5, or 19.4.2 or later, as appropriate for the deployed release line. Prioritize instances that process CI/CD configurations from untrusted sources.

fixed in 19.2.8, 19.3.5, 19.4.2

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.
0.55%44th percentile
agent run time
1h 24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 01:05Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+8h34m
Δ 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-13 01:05Z
    cve_org: trigger signal, started the run
  2. 2026-10-13 08:43Z
    GitLab Patches CVSS 10.0 Flaw That Could Let Unauthenticated Users Run Server Code
  3. 2026-10-14 01:13Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1451",
  "cve_id": "CVE-2026-97229",
  "display_id": "CVE-2026-97229",
  "ghsa_id": "GHSA-9hj5-r43h-h3xg",
  "euvd_id": "EUVD-2026-98214",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Regular-expression validation flaw in GitLab CI/CD",
  "summary": "GitLab CE/EE versions before 19.2.8, 19.3.5, and 19.4.2 in their respective release lines are affected. If a CI/CD configuration containing a malicious regular expression is processed under the relevant conditions, an unauthenticated remote attacker may be able to run code on the GitLab server.",
  "mitigation": "Upgrade GitLab CE/EE to 19.2.8, 19.3.5, or 19.4.2 or later, as appropriate for the deployed release line. Prioritize instances that process CI/CD configurations from untrusted sources.",
  "vendor": "GitLab",
  "product": "GitLab",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 19.2, < 19.2.8",
        ">= 19.3, < 19.3.5",
        ">= 19.4, < 19.4.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "19.2.8",
        "19.3.5",
        "19.4.2"
      ],
      "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": 0.0055,
  "epss_percentile": 0.4479,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 84.12258605,
  "t0_at": "2026-10-13T01:05:46.166000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-13T09:39:17+00:00",
      "days": 0.356606875,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T01:05:46.166000+00:00",
      "url": "https://github.com/jburgess-r7/CVE-2026-97229-PoC"
    },
    "trigger_signal": {
      "at": "2026-10-13T01:05:46.166000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T01:05:46.166000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97229"
    }
  }
}

published 2026-10-13 01:47Z
last change 2026-10-21 10:52Z

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.