# CVE-2026-112779: Grav API Plugin before 1.0.42 Cache Exhaustion and Page Permission Bypass

> Unauthenticated attackers can exhaust server resources via translation caching, while authorized users can bypass page permission rules.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-5hrq-qph9-cjf6

## What is CVE-2026-112779?

CVE-2026-112779 is a critical denial of service vulnerability in getgrav grav-plugin-api, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grav API plugin (grav-plugin-api) 1.0.40 before 1.0.42 caches a full translation dictionary for every well-formed language code sent to the unauthenticated GET /api/v1/translations/{lang} endpoint, and 1.0.16 before 1.0.42 fails to check target and destination page rules in the sync and batch copy endpoints. Unauthenticated attackers can send small requests that each store about 560 KB to exhaust disk or APCu, while accounts with api.pages.write can overwrite translations or create pages that page-level rules deny.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-112779 being exploited?

There is no known exploitation of CVE-2026-112779 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112779 is a critical denial of service vulnerability in getgrav grav-plugin-api, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112779 in the wild and no public exploit code.

Affected product: getgrav grav-plugin-api. 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-112779/ (Markdown: https://insights.sbomify.com/CVE-2026-112779/index.md)
```

## Sources

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

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