Quick answers
- Is CVE-2026-116136 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116136 being exploited in the wild.
- How severe is CVE-2026-116136?
- Medium severity, with a CVSS score of 5.9, published 25 October 2026.
- Which products and versions are affected?
- ProjectSend 2.0.0 through 2.7.1.
- Is there a fix for CVE-2026-116136?
- 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-116136 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116136?
- 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.
Technical details
The FileVersions::link() method in ProjectSend contains incomplete authorization checks that fail to properly validate staff user permissions when linking file versions. An attacker with staff privileges can exploit this by linking to intermediate file revisions or assigning out-of-scope clients, which causes the moveAssignmentsToRoot() function to expose protected original files to unauthorized clients. The vulnerability requires authentication as a staff user.
Affected products
- ProjectSend ProjectSend 2.0.0 through 2.7.1
Timeline
- 2026-10-25: disclosed