CVE-2026-57567: Readest path traversal in file transfer commands

CVE-2026-57567 · Severity: high · CVSS 8.6 · Published 2026-11-04

Readest is a cross-platform ebook reader that uses Tauri for desktop builds. Prior to version 0.11.10, two file transfer commands in the application accepted user-controlled file paths without proper validation, allowing an attacker with JavaScript execution in the app's privileged context to read sensitive files like SSH keys or write malicious code to system startup locations. Exploitation requires either an application XSS vulnerability or a compromised renderer, but no validation was in place to prevent directory traversal attacks.

Technologies: Readest. Vendors: Readest.

Quick answers

Is CVE-2026-57567 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57567 being exploited in the wild.
How severe is CVE-2026-57567?
High severity, with a CVSS score of 8.6, published 4 November 2026.
Which products and versions are affected?
Readest before 0.11.10.
Is there a fix for CVE-2026-57567?
Yes: fixed in 0.11.10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57567 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-57567?
Check whether you run Readest at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 0.11.10

Technical details

The vulnerability exists in apps/readest-app/src-tauri/src/transfer_file.rs where download_file and upload_file commands pass webview-supplied file_path directly to File::create and File::open without validating against the Tauri filesystem scope, rejecting absolute paths, or blocking parent-directory traversal. An attacker with JavaScript execution in the privileged application origin could read arbitrary files readable by the process or write arbitrary content to any writable path, including overwriting trusted startup files or extracting application secrets. The issue is fixed in version 0.11.10 by implementing path validation that rejects relative paths and parent-directory traversal, then requires the path to be within the app's filesystem scope.

Affected products

  • Readest Readest before 0.11.10

Timeline

  • 2026-11-04: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.