CVE-2023-26491 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in rsshub. A fix is available for rsshub — see the affected versions and patch details below.
RSSHub is vulnerable to cross-site scripting (XSS) via unvalidated URL parameters
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26491.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
rsshubnpmDescription
RSSHub is an open source and extensible RSS feed generator. When the URL parameters contain certain special characters, it returns an error page that does not properly handle XSS vulnerabilities, allowing for the execution of arbitrary JavaScript code. Users who access the deliberately constructed URL are affected. This vulnerability was fixed in version c910c4d28717fb860fbe064736641f379fab2c91. Please upgrade to this or a later version, there are no known workarounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | rsshub | all versions | 1.0.0-master.c910c4dnpm install rsshub@1.0.0-master.c910c4d |
Affected Products
rsshubrsshubDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rsshub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rsshub to 1.0.0-master.c910c4d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26491 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-26491 in your dependencies?
Find it across npm, including transitive dependencies.