CVE-2026-116136 projectsend CVE debrief

Who should care

Defenders responsible for ProjectSend installations, particularly those using versions 2.0.0 through 2.7.1, should assess exposure and prioritize remediation. This includes verifying the affected versions, assessing the vulnerability's impact on their systems, and ensuring proper authorization for file sharing. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-116136 is a medium-severity vulnerability in ProjectSend that allows staff users to share files without authorization. Defenders should prioritize verifying and remediating this vulnerability, focusing on restricting file version linking and ensuring proper authorization for file sharing.

• Potential exposure of protected files to unauthorized clients
• Need for verification of affected versions and remediation
• Possible unauthorized file sharing through linked file versions
• Requirement for enhanced monitoring of file sharing activity

Technical summary

The vulnerability exists in the FileVersions::link() function of ProjectSend, allowing staff users to link file versions without proper authorization. This can lead to exposure of protected original files to unauthorized clients. The vulnerability affects ProjectSend versions 2.0.0 through 2.7.1. Defenders should prioritize verifying and remediating this vulnerability, focusing on restricting file version linking and ensuring proper authorization for file sharing. The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions, exploitation, and remediation is limited.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in ProjectSend installations, focusing on restricting file version linking and ensuring proper authorization for file sharing.

Recommended defensive actions

• Verify ProjectSend version and restrict file version linking
• Ensure proper authorization for file sharing
• Monitor for suspicious file sharing activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions, exploitation, and remediation is limited. Defenders should verify the affected versions and assess the vulnerability's impact on their systems. The vulnerability exists in the FileVersions::link() function of ProjectSend, allowing staff users to link file versions without proper authorization. This can lead to exposure of protected original files to unauthorized clients. There is no evidence of public exploitation, but a

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.