CVE-2026-65895
Authenticated users can alter Grav API plugin rate-limiting and CORS settings.
Is CVE-2026-65895 being exploited?
Not confirmed. CVE-2026-65895 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-65895?
CVE-2026-65895 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65895?
Yes. A fix has been recorded for CVE-2026-65895. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65895 affect?
CVE-2026-65895 affects Grav CMS API Plugin (< 1.0.10), Grav CMS instances using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65895?
Upgrade Grav API Plugin to >=1.0.10 and review api.config.write privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with api.config.write can disable site-wide rate limiting (enable credential brute-force) and add attacker-controlled CORS origins with credentials to steal tokens.
Immediate action required
- affected< 1.0.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.