CVE-2026-62386
Grav API plugin leaks JWTs via URL, exposing admin tokens in logs and refs.
Is CVE-2026-62386 being exploited?
Not confirmed. CVE-2026-62386 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-62386?
CVE-2026-62386 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-62386?
Yes. A fix has been recorded for CVE-2026-62386. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62386 affect?
CVE-2026-62386 affects getgrav/grav-plugin-api (<1.0.0-rc.16), Grav CMS sites using the API plugin, Web servers/CDNs/proxies storing access logs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62386?
Upgrade to >=1.0.0-rc.16, revoke/rotate tokens, stop using ?token=, purge logs/CDN caches
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Leaked JWTs allow unauthorized API access: read configs/users, create admin accounts, change settings, delete pages.
Immediate action required
- affected< 1.0.0-rc.16
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.