CVE-2026-110623
7.5HighPublished 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-862
Impact
Authenticated users can read, modify, or delete any user's documents and revoke existing shares. To exploit this, an attacker only needs a low-privileged account to supply arbitrary document UUIDs to the shared nodes API.
Root cause
The shared nodes API endpoints lack authorization checks to verify whether the requester owns or has rights to share the target node UUID.
Affected systems
Papermerge Core through 3.5.3
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to a fixed version beyond 3.5.3 or apply commit 0fd469102b05b5ebeb5ee39b3f73ff76991ab269; if patching must wait, block or restrict access to POST /shared-nodes and PATCH /shared-nodes/access/ at your reverse proxy.
$ pip install --upgrade papermerge-coreAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Papermerge Core through 3.5.3 contains a missing authorization vulnerability in the shared nodes API that allows authenticated users to share other users' documents by supplying arbitrary node UUIDs. Attackers can call POST /shared-nodes or PATCH /shared-nodes/access/{node_id} to grant themselves any role, then read, modify, or delete victims' documents and revoke existing shares.
References
- https://github.com/papermerge/papermerge-core/blob/3.5.3/papermerge/core/features/shared_nodes/router.py#L78-L150
- https://github.com/papermerge/papermerge-core/commit/0fd469102b05b5ebeb5ee39b3f73ff76991ab269
- https://github.com/papermerge/papermerge-core/issues/1290
- https://github.com/papermerge/papermerge-core/issues/1291
- https://www.vulncheck.com/advisories/papermerge-core-through-3.5.3-missing-authorization-in-shared-nodes-api