CVE-2026-61450 - Grav before 2.0.2 contains a Twig sandbox bypass that allows a page author (any admin.pages user, or anyone ab

CVE-2026-61450 + Grav before 2.0.2 contains a Twig sandbox bypass that allows a page author (any admin.pages user, or anyone ab + High + 2026-07-10

One-sentence business risk

Broken authentication or authorization can expose tenant data and administrator actions, which buyers treat as a release blocker.

Research notes

  • Root cause: 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.
  • Affected versions: getgrav grav: 0 to < 2.0.2.
  • Fixed / safe versions: 2.0.2.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 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.

Exact vulnerable code pattern

Template(user_supplied_template).render(context)

Fixed / mitigated code pattern

render only named, repository-owned templates and pass user input as escaped data, not template source

Dependency or runtime update:

composer show affected component || true
composer require affected component --with-all-dependencies
composer audit

Step-by-step integration guide

  1. Inventory affected component across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to 2.0.2 or apply the exact vendor patch referenced below.
  3. Replace the vulnerable template-injection pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-61450-grav-before-2-0-2-contains-a-twig-sandbox-bypass
source: "MITRE CVE List V5"
dependency_or_product: "affected component"
affected: "getgrav grav: 0 to < 2.0.2"
fixed: "2.0.2"
signals:
  - "template-injection"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-61450 (Grav before 2.0.2 contains a Twig sandbox bypass that allows a page author (any admin.pages user, or anyone ab) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to 2.0.2. Replace the vulnerable template-injection pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-61450, template-injection, affected component, MITRE CVE List V5.
  • Affected tech stack: php/composer.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References