Quick answers
- Is CVE-2026-116871 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116871 being exploited in the wild.
- How severe is CVE-2026-116871?
- High severity, with a CVSS score of 7.5, published 27 October 2026.
- Which products and versions are affected?
- SemanticMediaWiki Semantic MediaWiki 3.0.0 before 7.3.1.
- Is there a fix for CVE-2026-116871?
- Yes: fixed in 7.3.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116871 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116871?
- Check whether you run SemanticMediaWiki Semantic MediaWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.3.1
Technical details
The LegacyParser::getSubqueryDescription() function in Semantic MediaWiki processes nested query tokens recursively without enforcing depth limits before descending, allowing an attacker to trigger stack exhaustion via the action=ask API. An unauthenticated network attacker can craft malicious query parameters with excessive nesting depth to exhaust server resources. The fix enforces query depth validation before recursion rather than only pruning the finished tree.
Affected products
- SemanticMediaWiki Semantic MediaWiki 3.0.0 before 7.3.1
Timeline
- 2026-10-27: disclosed