getgrav grav-plugin-api Flaw (CVE-2026-112779) Rated CVSS 9.3
A newly published critical vulnerability in getgrav grav-plugin-api carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2026-112779 affects getgrav grav-plugin-api.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
A critical security flaw tracked as CVE-2026-112779 has been published in the National Vulnerability Database for getgrav grav-plugin-api, with a CVSS base score of 9.3.
At a glance
- CVE
- CVE-2026-112779
- Product
- getgrav grav-plugin-api
- CVSS
- 9.3 Critical
- Weakness
- CWE-770
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Getgrav | grav-plugin-api | before 1.0.42 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-112779
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-112779?
CVE-2026-112779 is a CWE-770 vulnerability in getgrav grav-plugin-api.
How severe is CVE-2026-112779?
It has a CVSS score of 9.3 Critical.
Is CVE-2026-112779 being exploited?
There is no public confirmation of exploitation at the time of publication.
