CVE-2026-105314 json
Papermerge 3.5.3 allows remote code execution by a standard user via directory traversal in a /api/documents/upload call.
published last mo. modified last mo. also EUVD-2026-92275
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Papermerge 3.5.3 allows remote code execution by a standard user via directory traversal in a /api/documents/upload call. A Python .pth file can be written to site-packages, and its code is executed upon the next start of the Python interpreter.
Is CVE-2026-105314 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/kashishtopi/cve-pocs/blob/main/papermerge-core-arbitrary-file-write-rce/HR-papermerge-core-path-traversal-rce.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Papermerge Papermerge
Classification
- Weakness
-
- CWE-24 Path Traversal: '../filedir'
References
-
github.com
/kashishtopi/cve-pocs/blob/main/papermerge-core-arbitrary-file-write-rce/HR-papermerge-core-path-traversal-rce
exploit, technical-description
-
github.com
/papermerge/papermerge-core/blob/master/papermerge/core/features/document/router.py
technical-description
-
github.com
/papermerge/papermerge-core/blob/master/papermerge/core/pathlib.py
technical-description
- github.com /kashishtopi/cve-pocs/tree/main/papermerge-core-arbitrary-file-write-rce
Sources
- CVE List CVE-2026-105314
- NVD CVE-2026-105314
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.