CVE-2026-66416
CSRF in Leantime 3.6.2 allows forged state-changing requests via authenticated users.
Is CVE-2026-66416 being exploited?
Not confirmed. CVE-2026-66416 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.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-66416?
CVE-2026-66416 is rated High with a CVSS score of 8.6. 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-66416?
Yes. A fix has been recorded for CVE-2026-66416. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66416 affect?
CVE-2026-66416 affects Leantime 3.6.2 (self-hosted). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66416?
Restore Laravel VerifyCsrfToken middleware or apply vendor patch; force re-login and monitor access logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated CSRF can force authenticated users' browsers to perform POST/PUT/DELETE to create/delete projects, change settings and permissions.
Immediate action required
- affected<= 3.6.2
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.