# CVE-2026-85604: Grav before 2.0.18 Remote Code Execution via sort filter

> Authenticated users with page-write rights can execute arbitrary PHP code via the Twig sort filter in Grav CMS.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-ggph-mfjj-69jr, GHSA-p6qj-p5m7-f62h

## What is CVE-2026-85604?

CVE-2026-85604 is a high-severity code injection vulnerability in getgrav grav, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grav before 2.0.18 (affected versions <= 2.0.17) contains a remote code execution vulnerability in the Twig sort filter. The sortFunc wrapper in GravExtension.php hardcodes Twig's isSandboxed argument to false, so unlike |map/|filter/|reduce, |sort accepts a plain function name inside the sandbox; the remaining denylist misses spl_autoload, which performs a PHP include. An authenticated user with only page-write rights (admin.pages or api.pages.write) can supply a crafted payload (e.g., via form frontmatter rendered by the Email plugin) that invokes spl_autoload through the sort filter, resulting in arbitrary PHP execution as the web server user.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-85604 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85604 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85604 is a high-severity code injection vulnerability in getgrav grav, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85604 exists.

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-85604/ (Markdown: https://insights.sbomify.com/CVE-2026-85604/index.md)
```

## Sources

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

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