Quick answers
- Is CVE-2026-89261 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89261 being exploited in the wild.
- How severe is CVE-2026-89261?
- Medium severity, with a CVSS score of 6.5, published 11 September 2026.
- Which products and versions are affected?
- MoguBlog MoguBlog through 6.2.
- Is there a fix for CVE-2026-89261?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89261 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-89261?
- Check whether anything you run is named in the advisory. 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.
Technical details
The vulnerability is an authentication bypass in the mogu_search microservice that exposes Elasticsearch index management endpoints (POST /search/initElasticSearchIndex and related endpoints) without requiring credentials. The root cause is overly permissive security configuration in WebSecurityConfig.java that applies permitAll() to /search/** routes before the generic authenticated() check is evaluated. Remote attackers can invoke POST endpoints to delete the entire ES index, recreate it, modify mappings, inject malicious documents, or delete specific entries, resulting in degraded or poisoned search functionality. The vulnerability requires network access to the mogu_search service (typically http://127.0.0.1:8604) but no authentication or user interaction. No patch availability is documented in the advisory.
Affected products
- MoguBlog MoguBlog through 6.2
Timeline
- 2026-09-11: disclosed