Quick answers
- Is CVE-2026-57565 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57565 being exploited in the wild.
- How severe is CVE-2026-57565?
- Medium severity, with a CVSS score of 6.5, published 4 November 2026.
- Which products and versions are affected?
- Readest prior to 0.11.10.
- Is there a fix for CVE-2026-57565?
- Yes: fixed in 0.11.10. Until then: Upgrade to version 0.11.10 or later, which adds the isSafeObjectKeyName validation helper to reject path traversal sequences in filenames before constructing storage keys. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57565 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57565?
- 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
Upgrade to version 0.11.10 or later, which adds the isSafeObjectKeyName validation helper to reject path traversal sequences in filenames before constructing storage keys.
Technical details
The /api/storage/upload endpoint constructs an object storage key by concatenating an authenticated user's identifier with a client-supplied fileName parameter without validating for path separators or parent-directory traversal sequences. When the R2 backend places this key into a presigned PUT request URL, URL normalization collapses ".." components, allowing an attacker to escape their namespace prefix. An authenticated attacker who knows a target user's identifier and book hash can overwrite that user's stored book object and corrupt associated metadata.
Affected products
- Readest Readest prior to 0.11.10
Timeline
- 2026-11-04: disclosed
- 2026-06-18: patched