CVE Intelligence
High Denial of service

CVE-2026-40104 — XWiki's REST APIs can list all pages/spaces, leading to unavailability

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Versions 1.8-rc-1, 17.0.0-rc-1 and 17.5.0-rc-1 and prior include a resource exhaustion vulnerability in REST API endpoints such as /xwiki/rest/wikis/xwiki/spaces/AnnotationCode/pages/AnnotationConfig/objects/AnnotationCode.AnnotationConfig/0/properties, which list all available pages as part of the metadata for database list properties without applying query limits. On large wikis, this can exhaust available server resources. This issue has been patched in versions 16.10.16, 17.4.8 and 17.10.1.

Published Apr 15, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.7% (30-day exploitation probability)+8
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.7%
ahead of 52% of scored CVEs · Oct 14, 2026
Affects
Xwiki
Org.xwiki.platform:xwiki-platform-legacy-oldcore and 2 more
CVSS base
8.2
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Xwiki Org.xwiki.platform:xwiki-platform-legacy-oldcore, Xwiki Org.xwiki.platform:xwiki-platform-oldcore, Xwiki Xwiki).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Xwiki Org.xwiki.platform:xwiki-platform-legacy-oldcore version >= 1.8-rc-1, < 16.10.16version >= 17.0.0-rc-1, < 17.4.8version >= 17.5.0-rc-1, < 17.10.1 Vulnerable CVE Program (cve.org) e CISA ADP
Xwiki Org.xwiki.platform:xwiki-platform-oldcore version >= 1.8-rc-1, < 16.10.16version >= 17.0.0-rc-1, < 17.4.8version >= 17.5.0-rc-1, < 17.10.1 Vulnerable CVE Program (cve.org) e CISA ADP
Xwiki Xwiki ≥ 1.8 and < 16.10.16≥ 17.0.0 and < 17.4.8≥ 17.5.0 and < 17.10.1 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
6.9 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
8.2 CVSS 3.1 High 3.9 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
8.2 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-770 · Allocation of Resources Without Limits or Throttling

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.70%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · xwiki/org.xwiki.platform:xwiki-platform-oldcore, xwiki/org.xwiki.platform:xwiki-platform-legacy-oldcore
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.2
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Apr 15, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

Xwiki
every CVE for this vendor
CWE-770
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-40105 XWiki has Reflected Cross-Site Scripting (XSS) in its page history compare functionality Apr 15, 2026
  • Critical CVE-2026-33229 XWiki Platform affected by remote code execution with script right through unprotected Velocity scripting API Apr 8, 2026
  • Medium CVE-2026-26000 XWiki Platform affected by click-jacking through CSS injection in comments Feb 12, 2026
  • Medium CVE-2026-24128 XWiki Affected by Reflected Cross-Site Scripting (XSS) in Error Messages Jan 23, 2026
  • Medium CVE-2025-66472 XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication Dec 10, 2025
  • High CVE-2025-66473 XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis Dec 10, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-40104 is "XWiki's REST APIs can list all pages/spaces, leading to unavailability", rated High. It affects Org.xwiki.platform:xwiki-platform-legacy-oldcore (Xwiki); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. EPSS 0.70% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.