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

Published Nov 4, 2026
·
Updated

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 filekey metadata; the exact cross-tenant escape was verified for the R2 backend. This issue is fixed in version 0.11.10.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Readest to a version that resolves this vulnerability.

    Fixed in 0.11.10

Event History

Nov 4, 2026
CVE Published
via OSV·09:45 PM
Data Sourced
via OSV·09:45 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which storage backend has confirmed cross-tenant impact?

The cross-tenant namespace escape was verified for the R2 backend. The advisory does not establish the same impact for other storage backends.

2

What does an attacker need to exploit this issue?

An attacker must be authenticated and must know the target user's identifier and book hash. They can use a client-controlled fileName containing path traversal components to obtain a presigned PUT targeting another tenant's object.

3

What is the likely impact if exploitation succeeds?

An attacker can overwrite or poison another user's stored book object and corrupt the related file_key metadata. The reported impact is integrity loss; no confidentiality or availability impact is stated.

4

What version remediates the issue?

Upgrade Readest to version 0.11.10 or later. Versions prior to 0.11.10 are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203