Readest: Unscoped Tauri IPC download_file/upload_file allow arbitrary local file write and read from the webview
Affects Readest desktop builds (Linux, macOS, Windows) using the Tauri app before 0.11.10. The listed fixed version is 0.11.10.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.11.10
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Desktop (Linux/macOS/Windows) Tauri build of Readest JavaScript execution in the app/privileged origin (via XSS, a compromised renderer, or possibly book-embedded script) Commands are registered in the global invoke handler and reachable by the main, updater, and reader-* windows
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-57567 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects readest; fixed in 0.11.10.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.11.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Readest's desktop builds contain an unrestricted file download and upload command that lets JavaScript in the app's privileged window write attacker-controlled content to any path the process can write, or read and send any file it can read. A local attacker needs no login but does need a user to act, and must first run JavaScript in that privileged origin, such as through an app XSS flaw or a compromised renderer, to overwrite startup files or expose keys, tokens, and secrets.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Desktop (Linux/macOS/Windows) Tauri build of Readest JavaScript execution in the app/privileged origin (via XSS, a compromised renderer, or possibly book-embedded script) Commands are registered in the global invoke handler and reachable by the main, updater, and reader-* windowsUpgrade to a fixed version: 0.11.10.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- readest readest
fixed in 0.11.10
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-57567
Is CVE-2026-57567 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The file download and upload commands in the app's Tauri bridge are not limited to specific paths. JavaScript running in the app's privileged context can therefore write to and read from arbitrary files on the local machine.Source: github.com
Which versions are affected by CVE-2026-57567?
readest: before 0.11.10.Source: cve.now feed data
Am I affected, and how do I check?
The listed affected product is the Readest desktop Tauri build on Linux, macOS, and Windows, with versions before 0.11.10. To check a installation, look at the app version shown in its About or settings screen.Source: github.com
How do I fix CVE-2026-57567?
Update Readest to 0.11.10 or later, which is the listed fixed version.Source: github.com