Skip to main content
← Vulnerabilities

Readest: Unauthenticated SSRF / open request proxy in /api/opds/proxy

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

9.3CriticalCNA
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.

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

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

Published
Last modified
Published
Not listed in CISA KEV
26/100 · provisional
Unclear
Fix
Fixed in 0.11.10
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

Readest, an ebook reader, has a flaw in its /api/opds/proxy route that lets anyone on the network, without logging in, use the server to fetch arbitrary URLs and return the responses. On self-hosted Node or Docker deployments with internal-network access, this can expose cloud metadata and internal service responses.

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 unauthenticated /api/opds/proxy route in apps/readest-app/src/app/api/opds/proxy/route.ts accepted an attacker-controlled URL and fetched it server-side without restricting the scheme, blocking private, loopback, link-local, or metadata hosts, or revalidating destinations during automatic redirect following. The route also accepted caller-controlled outbound headers and Authorization values and reflected the upstream status and response body. A remote attacker could use the service as an open request proxy and, on Node, Docker, or other self-hosted deployments with internal-network access, retrieve cloud metadata or internal-service responses. Cloudflare Workers deployments restrict access to link-local and private destinations, which reduces the internal-network impact there, but the unauthenticated public fetch-and-reflect behavior remains. 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
  3. Posted on X 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-57566

Is CVE-2026-57566 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-57566?

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

How do I fix CVE-2026-57566?

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