CVE-2025-66473: XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis
Impact XWiki's REST API doesn't enforce any limits for the number of items that can be requested in a single request at the moment. Depending on the number of pages in the wiki and the memory configuration, this can lead to slowness and unavailability of the wiki. As an example, the /rest/wikis/xwiki/spaces resource returns all spaces on the wiki by default, which are basically all pages.
Patches XWiki 17.7.0RC1, 17.4.4 and 16.10.11 introduce a configurable limit, limiting responses to 1000 items by default. Requesting larger limits leads to an error now.
Workarounds We're not aware of any workaround, except denying access to the affected REST resources in a proxy in front of XWiki.
Other sources
XWiki is an open-source wiki software platform. Versions 16.10.10 and below, 17.0.0-rc-1 through 17.4.3 and 17.5.0-rc-1 through 17.6.0 contain a REST API which doesn't enforce any limits for the number of items that can be requested in a single request at the moment. Depending on the number of pages in the wiki and the memory configuration, this can lead to slowness and unavailability of the wiki. As an example, the /rest/wikis/xwiki/spaces resource returns all spaces on the wiki by default, which are basically all pages. This issue is fixed in versions 17.4.4 and 16.10.11.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66473?
CVE-2025-66473 has a moderate severity level due to potential resource exhaustion affecting the XWiki REST API.
How do I fix CVE-2025-66473?
To fix CVE-2025-66473, upgrade to one of the patched versions: 17.7.0-rc-1, 17.4.4, or 16.10.11.
Which XWiki versions are affected by CVE-2025-66473?
CVE-2025-66473 affects XWiki versions from 17.0.0-rc-1 to 17.5.0-rc-1 and prior to 16.10.11.
What kind of impact does CVE-2025-66473 have on XWiki?
CVE-2025-66473 can lead to performance issues such as slowness and potential unavailability of the XWiki instance.
Is there a workaround for CVE-2025-66473?
Currently, there are no specific workarounds for CVE-2025-66473 other than upgrading to the latest secure version.