CVE-2026-76839
Template sandbox bug exposes hashed passwords and 2FA secrets
Is CVE-2026-76839 being exploited?
Not confirmed. CVE-2026-76839 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-76839?
CVE-2026-76839 is rated High with a CVSS score of 8.7. 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-76839?
Yes. A fix has been recorded for CVE-2026-76839. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76839 affect?
CVE-2026-76839 affects Grav CMS (< 2.0.16), Twig sandboxed templates, Sites using Grav user accounts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76839?
Upgrade Grav to >=2.0.16; rotate user passwords and 2FA secrets; restrict editor access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated page-editors can call offsetGet on User objects to retrieve hashed passwords and 2FA secrets, enabling offline cracking and account takeover.
Immediate action required
- affected< 2.0.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.