# CVE-2026-61450: Grav before 2.0.2 Config Exfiltration via offsetGet Filter

> A Twig sandbox bypass in Grav allows page authors to exfiltrate configuration secrets like API keys and credentials via object serialization filters.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-xg8j-6m35-m6wr

## What is CVE-2026-61450?

CVE-2026-61450 is a high-severity vulnerability in getgrav grav, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav before 2.0.2 contains a Twig sandbox bypass that allows a page author (any admin.pages user, or anyone able to write to user/pages) to exfiltrate configuration secrets. Although the sandbox replaces the 'config' variable with a redacted facade and strips Config::get/toArray from the method allowlist, the raw container remains accessible via the allow-listed grav.offsetGet('config'), which returns the real Config object. Allow-listed object-dumping filters (json_encode, print_r, yaml_encode) then serialize that object at the PHP level without invoking the sandbox method gate, exposing the full config tree including plugin secrets such as SMTP credentials, API keys, and plugin DB credentials. This is an incomplete fix for GHSA-j274-39qw-32c9.

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

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


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

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

## Is CVE-2026-61450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61450 is a high-severity vulnerability in getgrav grav, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61450 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-61450/ (Markdown: https://insights.sbomify.com/CVE-2026-61450/index.md)
```

## Sources

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

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