# CVE-2026-100671: Grav before 2.0.25 Session Cookie Theft via Twig Sandbox

> Attackers with page-write permissions can steal administrator session cookies via Twig sandbox flaws, enabling account takeover.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-jcv9-gfgx-wjw4, GHSA-pp89-h475-7gj6

## What is CVE-2026-100671?

CVE-2026-100671 is a high-severity vulnerability in getgrav grav, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Grav is a flat-file CMS. In versions 2.0.19 through 2.0.24 — and in 2.0.0 through 2.0.18 and 1.7.x only where content Twig has been explicitly enabled — page content authored by a user holding only page-write permission is rendered through a Twig sandbox that allowlists get_cookie(), which returns any cookie sent with the current request, including the visitor's session cookie. Because the read occurs server-side via filter_input(INPUT_COOKIE, ...), the HttpOnly, Secure and SameSite attributes offer no protection. Grav then stores the finished post-Twig output in a page-content cache keyed only on page identity and the configuration checksum, with no session, user or request dimension and no bypass for authenticated visitors. A page published by a page-write user can therefore capture the session identifier of the next administrator who views it, after which the cached output serves that identifier to unauthenticated visitors, who can replay the cookie to authenticate as that administrator. Since 2.0.19, security.twig_content.process_enabled defaults to true and Security::applyTwigContentDefault() derives each page's process.twig flag from that gate, so content Twig runs on every page with no frontmatter or operator action. Fixed in 2.0.25; 1.7.x is outside the backport scope.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-100671 being exploited?

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

Public exploit code:

- https://github.com/canhieu/cve-2026-100671-poc (github_poc): https://github.com/canhieu/cve-2026-100671-poc

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100671 is a high-severity vulnerability in getgrav grav, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100671 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-100671/ (Markdown: https://insights.sbomify.com/CVE-2026-100671/index.md)
```

## Sources

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

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