Quick answers
- Is CVE-2026-8786 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8786 being exploited in the wild.
- How severe is CVE-2026-8786?
- Medium severity, with a CVSS score of 6.3, published 18 May 2026.
- Which products and versions are affected?
- Tencent WeKnora up to 0.3.6.
- Is there a fix for CVE-2026-8786?
- 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-8786 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8786?
- Check whether you run Tencent WeKnora 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.
Technical details
An Insecure Direct Object Reference (IDOR) vulnerability exists in the InitializationHandler of Tencent WeKnora up to version 0.3.6. The function 'getKnowledgeBaseForInitialization' in 'internal/handler/initialization.go' retrieves knowledge base entities using only the 'kbId' without verifying if the entity belongs to the requesting user's 'TenantID'. An authenticated attacker can exploit this by sending crafted GET, PUT, or POST requests to the '/api/v1/initialization/config/{kbId}' or '/api/v1/initialization/kb/{kbId}' endpoints. This allows the attacker to read or modify configurations such as chunk sizes, separators, and LLM models for any knowledge base on the system.
Affected products
- Tencent WeKnora up to 0.3.6
Timeline
- 2026-04-06: disclosed: Public exploit and advisory published on GitHub Gist
- 2026-05-18: advisory: NVD and VulDB publish advisory details