External risk intelligence

Grav API Plugin Cache Exhaustion and Page Rule Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-112779

The vulnerability affects an API endpoint within the Grav API plugin. As this is a web-based API plugin for a content management system, it is commonly deployed as part of an internet-facing web application. The nature of the vulnerable endpoints, specifically an unauthenticated GET request, makes it a likely candidate for public internet exposure in typical web deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical security vulnerability in the Grav API plugin that could allow unauthenticated attackers to exhaust server disk space or overload the cache. For authenticated users with specific permissions, the flaw also enables unauthorized overwriting of content or creation of pages that bypass established rules. The primary concern is confirming the plugin's relevance and exposure within your environment.

  • Attackers can overload server resources.
  • Leadership should remember potential for data compromise.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could initiate a series of requests to the Grav API plugin, starting from the internet, to exploit vulnerabilities in how it handles translations and page content. By sending well-formed requests to the `GET /api/v1/translations/{lang}` endpoint, an unauthenticated attacker can cause the plugin to cache large amounts of data, potentially filling up disk space or memory. Alternatively, an attacker who has authenticated access with `api.pages.write` permissions could abuse the sync and batch copy endpoints to overwrite existing content or create new pages that violate access rules.

  • Unauthenticated access to API
  • Sending crafted language code requests
  • Disk space exhaustion or content manipulation

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could affect the disk space or APCu cache of a Grav CMS installation. Unauthenticated attackers can exhaust disk space by repeatedly requesting translation dictionaries. Accounts with API write permissions could potentially overwrite existing translations or create unauthorized pages, bypassing page access rules.

  • Disk space and cache may be exhausted.
  • Malicious requests can fill storage.
  • Service disruption or unauthorized content.

Operational Fix

Recommended remediation, mitigation, and detection steps

Grav API plugin instances accessible via the internet are at risk. Application owners and platform teams should prioritize identifying deployments of this plugin, confirming exposure and business criticality, and then coordinating remediation with the vendor.

  • Identify Grav API plugin instances and exposure.
  • Confirm accountable owners and business criticality.
  • Plan remediation based on vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Grav API plugin?

The Grav API plugin is a software component designed for the Grav Content Management System (CMS). It extends the CMS by providing an interface that allows external applications to programmatically interact with Grav, such as managing pages, content, and system translations through web-based API endpoints.

What is the weakness class for CVE-2026-112779?

This vulnerability is classified as CWE-770, which is 'Allocation of Resources Without Limits or Throttling.' In this specific case, the plugin fails to properly limit the amount of memory or disk space consumed when processing requests, allowing the system to be overwhelmed by excessive resource allocation.

How do attackers trigger this vulnerability?

An unauthenticated attacker triggers the resource exhaustion by sending specific GET requests to the translation API endpoint, forcing the server to cache large dictionaries for every language code provided. Note that simply browsing the site normally does not trigger this; it requires crafted API requests specifically designed to inflate cache storage.

Is my site at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a 'Likely' risk because the Grav API plugin is typically deployed in internet-facing web applications. Since the vulnerability involves an unauthenticated API endpoint, systems accessible from the public internet are considered to have a higher potential for exposure compared to those restricted to internal networks.

When should I update the Grav API plugin?

You should prioritize updating as soon as you confirm the plugin is in use. Begin by identifying all instances of the Grav API plugin within your environment, confirm which are internet-facing, and coordinate with your team to apply the vendor-provided security updates that resolve these caching and permission-checking flaws.

References