Quick answers
- Is CVE-2026-112003 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112003 being exploited in the wild.
- How severe is CVE-2026-112003?
- Medium severity, with a CVSS score of 5.9, published 18 October 2026.
- Which products and versions are affected?
- ProjectSend 2.0.0 before 2.7.0.
- Is there a fix for CVE-2026-112003?
- Yes: fixed in ProjectSend 2.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112003 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112003?
- Check whether you run ProjectSend 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: ProjectSend 2.7.0
Technical details
The OrphanFileScanner::isOrphan() method fails to canonicalize file paths before comparing them against tracked files in the database. An attacker with import_orphans permission can submit path aliases like "./" sequences that the Flysystem storage layer normalizes differently, causing legitimately tracked files to appear as orphans. This allows deletion or adoption of other owners' files while circumventing the delete_others_files access control check.
Affected products
- ProjectSend ProjectSend 2.0.0 before 2.7.0
Timeline
- 2026-10-18: disclosed
- 2026-10-18: patched: Fix in commit 1e34773: isOrphan() now refuses paths that the storage normalizer would rewrite