CVE-2026-116019

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

GHSA-8xfc-f7mm-8g34 ↗EUVD-2026-109277 ↗

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.
getgrav grav >= 2.0.15, < 2.2.13
fixed in 2.2.13
ETK-2026-2555Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 14msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h27m
0
+2h
+4h
+8h
+10h
+12h

description

Grav versions 2.0.15 through 2.2.12 mishandle allowlist checks in Flex form overrides. An attacker who can edit pages may invoke unintended public static methods, potentially reading, replacing, or deleting files outside the intended page area.

mitigation

Upgrade Grav to version 2.2.13 or later. Until upgrades are complete, restrict page-edit permissions to trusted users.

fixed in 2.2.13

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-24 11:40Z
Δ 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-24 11:40Z
    ghsa: trigger signal, started the run
  2. 2026-10-24 11:40Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2555",
  "cve_id": "CVE-2026-116019",
  "display_id": "CVE-2026-116019",
  "ghsa_id": "GHSA-8xfc-f7mm-8g34",
  "euvd_id": "EUVD-2026-109277",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Allowlist bypass in Grav Flex form overrides",
  "summary": "Grav versions 2.0.15 through 2.2.12 mishandle allowlist checks in Flex form overrides. An attacker who can edit pages may invoke unintended public static methods, potentially reading, replacing, or deleting files outside the intended page area.",
  "mitigation": "Upgrade Grav to version 2.2.13 or later. Until upgrades are complete, restrict page-edit permissions to trusted users.",
  "vendor": "getgrav",
  "product": "grav",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.15, < 2.2.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.2.13"
      ],
      "package_name": "grav",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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": 35.594674483333336,
  "t0_at": "2026-10-24T11:40:35.632000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-24T11:40:35.632000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-24T11:40:35.632000+00:00",
      "url": "https://github.com/advisories/GHSA-8xfc-f7mm-8g34"
    }
  }
}

published 2026-10-24 17:31Z
last change 2026-10-24 22:20Z

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.