Denial of Service (DoS) vulnerability in RSSHub

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2022-31110: 1.60% estimated exploitation activity in the next 30 days; percentile 75.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Passing some special values to the filter and filterout parameters can cause an abnormally high CPU. Impact on the performance of the servers and RSSHub services. Patches It is fixed in 5c4177441417b44a6e45c3c63e9eac2504abeb5b , please update to this or the later versions as soon as possible. References Full report: https://github.com/DIYgod/RSSHub/issues/10045 For more information If you have any questions or comments about this advisory: Open an issue in <https://github.com/DIYgod/RSSHub/issues Email us at i@diygod.me Credits @Rongronggg9

Published by the source

23 Jun 2022, 06:45 UTC

Last modified by the source

8 Nov 2023, 04:09 UTC

Source last checked

26 Oct 2026, 12:24 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jvxx-v45p-v5vf

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jvxx-v45p-v5vf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-31110

Advisory: Denial of Service (DoS) vulnerability in RSSHub
IDs: CVE-2022-31110, GHSA-jvxx-v45p-v5vf
Record: https://patchnext.com/advisories/cve-2022-31110 (revision 2, source checked 26 Oct 2026, 12:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm rsshub: affected <= 1.0.0

## Suggested inspection (read-only)
- `npm ls rsshub --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rsshub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jvxx-v45p-v5vf (OSV record GHSA-jvxx-v45p-v5vf lists affected ranges: npm rsshub >=0 <=1.0.0)
- Verified: https://github.com/advisories/GHSA-jvxx-v45p-v5vf (GitHub-reviewed advisory GHSA-jvxx-v45p-v5vf lists affected ranges: npm rsshub >=0 <=1.0.0)

Commands are suggestions: review each one before running it.