CVE-2026-57562

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-117186 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an intuitive reading experience. Prior to 0.11.10, POST /api/stripe/check in apps/readest-app/src/app/api/stripe/check/route.ts accepted a client-controlled sessionId, retrieved the corresponding Stripe Checkout Session, and granted the paid plan to the authenticated caller without verifying session.metadata.userId. The createOrUpdateSubscription path then updated the plans row keyed by the caller's user identifier rather than the Checkout Session owner. Any authenticated free user with a paid active Checkout Session identifier, including one from the user's own single legitimate purchase, could replay that identifier to upgrade additional accounts without payment. This issue is fixed in version 0.11.10.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2026

Last Modified

November 12, 2026

Advisory Details (4)

Auto-updated Nov 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Subscription/entitlement hijack: /api/stripe/check binds any paid Checkout Session to the caller · Advisory · readest/readest · GitHub

https://github.com/readest/readest/security/advisories/GHSA-pv88-3727-j7v8
GitHub release Patch Available

Readest 0.11.10

Patch available: readest/readest v0.11.10

https://github.com/readest/readest/releases/tag/v0.11.10
GitHub pull request

fix(security): harden OPDS proxy SSRF, storage key validation, Stripe check

Fix merged in readest/readest PR #4638 on 2026-06-18 — awaiting tagged release

https://github.com/readest/readest/pull/4638
GitHub commit

commit 495783d04516 (readest/readest)

Fix landed in readest/readest commit 495783d04516 — awaiting tagged release

https://github.com/readest/readest/commit/495783d04516d05b2eb10f8f8bad297d436b36de

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-12 19:30 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-05 21:33 UTCEchelonGraph re-scored
  11. 2026-11-05 20:26 UTCEchelonGraph re-scored
  12. 2026-11-05 20:23 UTCEchelonGraph re-scored
  13. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-11-04 23:03 UTCENISA EUVD ID recordedEUVD-2026-117186 · Source: ENISA EUVD
  15. 2026-11-04 22:30 UTCEchelonGraph re-scored
  16. 2026-11-04 21:51 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  17. 2026-11-04 21:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57562?
CVE-2026-57562 is a medium-severity vulnerability; its CVE record was published on November 4, 2026. Readest is a modern, feature-rich ebook reader designed for seamless cross-platform access and an intuitive reading experience. Prior to 0.11.10, POST /api/stripe/check in apps/readest-app/src/app/api/stripe/check/route.ts accepted a client-controlled sessionId, retrieved the corresponding Stripe…
When was the CVE record for CVE-2026-57562 published?
The CVE record for CVE-2026-57562 was published on November 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-57562 actively exploited?
CVE-2026-57562 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57562?
CVE-2026-57562 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57562?
A fix for CVE-2026-57562 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57562

Explore →

Is Your Infrastructure Affected by CVE-2026-57562?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.