CVE-2026-53528
Authenticated path traversal in LeafWiki asset rename allows exfiltration of local files.
Is CVE-2026-53528 being exploited?
Not confirmed. CVE-2026-53528 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-53528?
CVE-2026-53528 is rated High with a CVSS score of 8.8. 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-53528?
Yes. A fix has been recorded for CVE-2026-53528. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53528 affect?
CVE-2026-53528 affects LeafWiki 0.3.0 - 0.10.0, Self-hosted LeafWiki instances, Server local files (databases, configs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53528?
Upgrade to LeafWiki >=0.10.1; restrict editor accounts; run process with least filesystem privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated editor can move local files into a page asset directory, making sensitive files (DB, configs) downloadable and enabling data theft.
Immediate action required
- affected>= 0.3.0 and < 0.10.1
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.