CVE-2026-57567 json
Readest: Unscoped Tauri IPC download_file/upload_file allow arbitrary local file write and read from the webview
published 28d ago modified 6d ago also EUVD-2026-117181 , GHSA-55vr-pvq5-6fmg
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository readest/readest. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an intuitive reading experience. In affected desktop Tauri builds prior to 0.11.10, the apps/readest-app/src-tauri/src/transfer_file.rs commands download_file and upload_file accepted a webview-controlled file_path and passed it to File::create or File::open without checking the Tauri filesystem scope, rejecting absolute paths, or blocking parent-directory traversal. The commands were registered in the global invoke handler for the main, updater, and reader-* windows, so JavaScript executing in the privileged application origin could write attacker-controlled content to any path writable by the process or read and send any path readable by the process. Exploitation requires JavaScript execution in that privileged origin, such as through an application XSS or compromised renderer; whether book-embedded JavaScript can reach the parent origin was not established. The write primitive can overwrite trusted or startup files, while the read primitive can expose keys, tokens, and application secrets. This issue is fixed in version 0.11.10.
Patch / fix
- github.com/readest/readest@4025c4d commit
- github.com/readest/readest@446c2c7 commit
- github.com/readest/readest#4639 pull request
- github.com/readest/readest#4651 pull request
- github.com/readest/readest/releases/tag/v0.11.10 release
Is CVE-2026-57567 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
- 6d ago
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/readest/readest/security/advisories/GHSA-55vr-pvq5-6fmg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
Affected products
- readest readest
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
- github.com /readest/readest/pull/4639
- github.com /readest/readest/pull/4651
- github.com /readest/readest/commit/4025c4d7b52c8c174ec1d4c02c2a864cce249604
- github.com /readest/readest/commit/446c2c72de198de2dfcd63589f549ca517961d15
-
github.com
/readest/readest/security/advisories/GHSA-55vr-pvq5-6fmg
exploit, advisory
- github.com /readest/readest/releases/tag/v0.11.10
Sources
- CVE List CVE-2026-57567
- NVD CVE-2026-57567
- Maintainer advisory GHSA-55vr-pvq5-6fmg
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.
The maintainers of readest/readest published their own advisory on GitHub. Reviewed sources take precedence over it.