Skip to main content
← Vulnerabilities

Readest: Cross-tenant object write via unsanitized fileName in /api/storage/upload (object-key path traversal)

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.11.10
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.11.10.

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-57565 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects readest; fixed in 0.11.10.

Published
Last modified
Published
Not listed in CISA KEV
10/100 · provisional
Fix
Fixed in 0.11.10
None on Exploit-DB, Metasploit or GitHub

Summary

Readest, a cross-platform ebook reader, has a path traversal flaw in its file upload API that lets a remote attacker with a low-privilege logged-in account write to another user's stored book files, requiring no action from the victim. An attacker who knows the target user's identifier and book hash can overwrite or corrupt that user's book data and its associated metadata.

Read the original description

Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an intuitive reading experience. Prior to 0.11.10, the apps/readest-app/src/pages/api/storage/upload.ts route constructed an object key from the authenticated user's identifier and a client-controlled fileName without rejecting path separators or parent-directory traversal. In the R2 backend, apps/readest-app/src/utils/r2.ts placed that key into a new Request URL before signing it, and URL normalization collapsed parent-directory components so the resulting presigned PUT could escape the caller's namespace. An authenticated attacker who knew a target user identifier and book hash could overwrite or poison that user's stored book object and corrupt the associated file_key metadata; the exact cross-tenant escape was verified for the R2 backend. This issue is fixed in version 0.11.10.

What to do

  • Upgrade to a fixed version: 0.11.10.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • readest readest

    fixed in 0.11.10

Evidence 4

  1. Advisory
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-57565

Is CVE-2026-57565 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

Which versions are affected by CVE-2026-57565?

readest: before 0.11.10.Source: cve.now feed data

How do I fix CVE-2026-57565?

Upgrade to a fixed version: 0.11.10.Source: cve.now feed data