Readwise Reader Android XSS via poisoned documents
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Three stored XSS flaws in Readwise Reader for Android allow attackers to execute JavaScript through malicious document metadata and SVG markup; version 8.10.1 patches the sanitizer issue.
Readwise Reader for Android versions up to 8.7.2 contain three stored cross-site scripting (XSS) vulnerabilities affecting document rendering. CVE-2026-18311 exploits insufficient HTML escaping in metadata fields like author and title; CVE-2026-18312 targets improper URL escaping in WebView construction for video fallbacks and paywalls; CVE-2026-18320 results from overly permissive SVG/PATH attribute rules in the sanitizer that allow script-capable attributes like onload and onerror.
An attacker who can create or modify documents accessible to the application—either through direct library access or by supplying poisoned content that users save—can inject arbitrary JavaScript that executes within the WebView context. This enables theft of stored documents, credentials, and session tokens. The vulnerabilities are stored, meaning malicious payloads persist in users' libraries and sync across devices.
Version 8.10.1 addresses the sanitizer-wildcard issue (CVE-2026-18320). Users should update immediately and exercise caution when adding content from untrusted sources. The vendor was unreachable at the time of disclosure.
Mentioned in this report
Source reporting: https://kb.cert.org/vuls/id/699627
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections with the Splunk SPL and Microsoft KQL already written, the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 10,177 reports from 155 sources, 1,803 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs