Grav has Insecure Deserialization in File Cache

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

1.3 · CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2026-7317: 0.22% estimated exploitation activity in the next 30 days; percentile 13.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Insecure Deserialization in File Cache - Severity: High - CWE: CWE-502 - Location: system/src/Grav/Framework/Cache/Adapter/FileCache.php - Sink: unserialize($value, ['allowedclasses' = true]) Affected version(s) - Affected: = 1.7.44 and <= 1.7.49.5 (verified in current codebase and changelog-covered releases). - Fixed: No upstream fix identified in the reviewed branch at the time of analysis. - Notes: Earlier 1.7.x releases may also be affected, but were not fully back-traced in this review. Notes allowedclasses = true allows object instantiation and does not constrain classes. PoC (Primitive Demonstration) Preconditions - Local PHP runtime. - Goal is to validate the deserialization primitive used in cache retrieval. Steps Expected Result - Output contains: FILECACHEUNSERIALIZETRIGGERED. Interpretation This reproduces the same unsafe primitive used by FileCache::doGet(): unserialize($value, ['allowedclasses' = true]). If cache files are attacker-tampered, object magic methods may…

Published by the source

5 May 2026, 21:29 UTC

Last modified by the source

8 May 2026, 15:36 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gwfr-jfjf-92vv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-7317

Advisory: Grav has Insecure Deserialization in File Cache
IDs: CVE-2026-7317, GHSA-gwfr-jfjf-92vv
Record: https://patchnext.com/advisories/cve-2026-7317 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: getgrav/grav 2.0.0-beta.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist getgrav/grav: affected < 2.0.0-beta.2; fixed in 2.0.0-beta.2

## Suggested inspection (read-only)
- Packagist getgrav/grav: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on getgrav/grav.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gwfr-jfjf-92vv (GitHub-reviewed advisory GHSA-gwfr-jfjf-92vv lists affected ranges: Packagist getgrav/grav >=0 <2.0.0-beta.2)

Commands are suggestions: review each one before running it.