Quick answers
- Is CVE-2026-113356 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113356 being exploited in the wild.
- How severe is CVE-2026-113356?
- High severity, with a CVSS score of 7.5, published 20 October 2026.
- Which products and versions are affected?
- DokuWiki before 2026-07-14c.
- Is there a fix for CVE-2026-113356?
- Yes: fixed in 2026-07-14c. Until then: Disable draft functionality by setting $conf['usedraft'] = 0; in DokuWiki's configuration, or restrict AUTH_CREATE permission to prevent untrusted users from triggering the race condition. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113356 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113356?
- Check whether you run DokuWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2026-07-14c
Disable draft functionality by setting $conf['usedraft'] = 0; in DokuWiki's configuration, or restrict AUTH_CREATE permission to prevent untrusted users from triggering the race condition.
Technical details
A race condition between concurrent reads and writes in DokuWiki's draft file handling allows an attacker to corrupt the serialized draft content during file_get_contents() by timing a concurrent file truncate and rewrite. The getDraftText() method passes the potentially corrupted file contents directly to unserialize() without restricting allowed object classes. Authenticated users with edit rights can exploit gadget chains like MemoryIndex (2026-07-14+) or Installer (2014-05-05+) to achieve arbitrary file write and code execution.
Affected products
- DokuWiki DokuWiki before 2026-07-14c
Timeline
- 2026-10-20: disclosed
- 2026-10-20: advisory