CVE-2026-116136 ProjectSend 2.0.0 through 2.7.1 Incorrect Authorization via File Version Linking
Medium 6.0
Published
Updated
Check this codebase for CVE-2026-116136 and fix it if it is affected.
What it is: CVE-2026-116136 is a medium-severity vulnerability in ProjectSend, published on 25 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-116136 in the wild and no public exploit code.
Affected product: ProjectSend. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-116136/ (Markdown: https://insights.sbomify.com/CVE-2026-116136/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116136?
CVE-2026-116136 is a medium-severity vulnerability in ProjectSend, published on 25 Oct 2026.
Official description
ProjectSend 2.0.0 through 2.7.1 contains an incomplete authorization vulnerability in FileVersions::link() that allows staff users to share files without authorization by linking file versions. Attackers can link their file onto an intermediate revision or assign out-of-scope clients, causing moveAssignmentsToRoot() to expose protected original files to unauthorized clients.
Weakness: CWE-863
Which versions are affected by CVE-2026-116136?
How do I fix CVE-2026-116136?
No fix has been published for CVE-2026-116136 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116136 being exploited?
There is no known exploitation of CVE-2026-116136 in the wild and no public exploit code.
Sources
Also known as GHSA-gjpq-2gcq-78q9.