CVE-2026-14814

validatedZero produced an exploit or a check.

GHSA-49c6-8ph4-9vr9 ↗EUVD-2026-98224 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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 < 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-625 Permissive Regular Expression
ETK-2026-1454Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.4dTTV
1h 04mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+33h57magent stopped
0
+12h
+24h
+36h

description

GitLab CE/EE versions in the affected release ranges can allow an authenticated user to poison cached responses for raw repository files because repository references are insufficiently validated. Where a targeted CI/CD pipeline consumes such a response, it may run attacker-controlled content and could expose protected environment variables.

mitigation

Upgrade GitLab to 19.2.8, 19.3.5, or 19.4.2, as appropriate for the maintained release line. Until upgraded, restrict untrusted users' ability to influence repositories or pipeline inputs that use raw repository files.

fixed in 19.2.8, 19.3.5, 19.4.2

check
available
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 01:08Z
Δ 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 check: a technique exists and was validated, 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:08Z
    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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1454",
  "cve_id": "CVE-2026-14814",
  "display_id": "CVE-2026-14814",
  "ghsa_id": "GHSA-49c6-8ph4-9vr9",
  "euvd_id": "EUVD-2026-98224",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Raw repository-file cache poisoning in GitLab",
  "summary": "GitLab CE/EE versions in the affected release ranges can allow an authenticated user to poison cached responses for raw repository files because repository references are insufficiently validated. Where a targeted CI/CD pipeline consumes such a response, it may run attacker-controlled content and could expose protected environment variables.",
  "mitigation": "Upgrade GitLab to 19.2.8, 19.3.5, or 19.4.2, as appropriate for the maintained release line. Until upgraded, restrict untrusted users' ability to influence repositories or pipeline inputs that use raw repository files.",
  "vendor": "GitLab",
  "product": "GitLab",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 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": [
    625
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": 0.0025,
  "epss_percentile": 0.1512,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 63.7371767,
  "t0_at": "2026-10-13T01:08:26.181000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-14T11:05:18.759925+00:00",
      "days": 1.414497441261574,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T01:08:26.181000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-13T01:08:26.181000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T01:08:26.181000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14814"
    }
  }
}

published 2026-10-13 02:31Z
last change 2026-10-21 21:36Z

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.