# CVE-2026-116019: Grav 2.0.15 before 2.2.13 Allowlist Bypass via Flex Form Override Directives


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-47gg-mh38-9rr7, GHSA-8xfc-f7mm-8g34

## What is CVE-2026-116019?

CVE-2026-116019 is a high-severity vulnerability in getgrav grav, published on 24 Oct 2026. 

### Official description

Grav 2.0.15 before 2.2.13 contains an allowlist bypass vulnerability that allows page editors to invoke arbitrary public static methods by relocating data-*@ directives with unset-name@ or integer keys. Attackers with page-edit permission can embed crafted fields in Flex form overrides in page frontmatter to call methods like Folder::delete or Utils::download, deleting directories, overwriting files, or reading files outside the page tree.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

## Which versions are affected by CVE-2026-116019?


## How do I fix CVE-2026-116019?

No fix has been published for CVE-2026-116019 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116019 being exploited?

There is no known exploitation of CVE-2026-116019 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116019 and fix it if it is affected.

What it is: CVE-2026-116019 is a high-severity vulnerability in getgrav grav, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116019 in the wild and no public exploit code.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116019/ (Markdown: https://insights.sbomify.com/CVE-2026-116019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116019
- OSV: https://osv.dev/vulnerability/CVE-2026-116019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116019/
Summaries are generated and may contain mistakes; the official description above is the record.