Quick answers
- Is CVE-2026-64836 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64836 being exploited in the wild.
- How severe is CVE-2026-64836?
- High severity, with a CVSS score of 8.8, published 10 September 2026.
- Which products and versions are affected?
- ICEcoder through 8.1.
- Is there a fix for CVE-2026-64836?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-64836 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-64836?
- Check whether you run ICEcoder 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.
Technical details
The vulnerability is a path traversal flaw in the file-control endpoint caused by a logic error in the document-root confinement check. The File::check() validation function compares the realpath() result to boolean true, which will never succeed, effectively disabling the security check. Authenticated attackers can exploit this by submitting path traversal sequences (e.g., ../../../) or absolute paths in the file parameter to bypass directory restrictions. An attacker can read, write, or delete files outside the configured document root. The vulnerability affects ICEcoder through version 8.1; the package is abandoned and no longer maintained.
Affected products
- ICEcoder ICEcoder through 8.1
Timeline
- 2026-09-10: disclosed