Quick answers
- Is CVE-2026-73699 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73699 being exploited in the wild.
- How severe is CVE-2026-73699?
- High severity, with a CVSS score of 7.2, published 10 September 2026.
- Which products and versions are affected?
- FileRun before 2026.3.0.
- Is there a fix for CVE-2026-73699?
- A patch was published on 2026-09-06: Fixed in FileRun 2026.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73699 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-73699?
- Check whether you run FileRun 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
CVE-2026-73699 is a PHP object injection (deserialization) vulnerability in the Perms::getPerms() method caused by improper use of unserialize(). The vulnerability occurs because the code passes a positional array instead of a named-key array to disable class instantiation, allowing attackers to instantiate arbitrary classes. While this vulnerability requires initial database write access, it is weaponized by CVE-2026-73698 (a SQL injection affecting delegated administrators) to write arbitrary files to web-accessible paths. The payload executes on every authenticated page load, making it a reliable exploitation vector. FileRun 2026.3.0 (released September 6, 2026) patches this vulnerability; prior versions including 2026.2.0 and 2026.2.1 are affected.
Affected products
- FileRun FileRun before 2026.3.0
Timeline
- 2026-09-10: disclosed
- 2026-09-06: patched: Fixed in FileRun 2026.3.0