# CVE-2026-91750: Tencent WeKnora SSRF via unvalidated HTTP redirects

Source: https://junglewise.ai/threats/cve-2026-91750-tencent-weknora-ssrf-via-unvalidated-http-redirects  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-91750 · Severity: medium · CVSS 6.5 · Published 2026-09-15

WeKnora is an open-source platform that processes raw documents for knowledge retrieval and reasoning. The system fails to validate where HTTP redirects lead when downloading documents from user-supplied URLs, allowing authenticated attackers to bypass security controls and access internal services and cloud metadata that should be blocked.

Technologies: [Tencent WeKnora](https://junglewise.ai/threats/technologies/weknora). Vendors: [Tencent](https://junglewise.ai/threats/vendors/tencent).

## Quick answers

**Is CVE-2026-91750 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-91750 being exploited in the wild.

**How severe is CVE-2026-91750?** Medium severity, with a CVSS score of 6.5, published 15 September 2026.

**Which products and versions are affected?** Tencent WeKnora before 0.7.0.

**Is there a fix for CVE-2026-91750?** 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-91750 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-91750?** 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

The vulnerability is a Server-Side Request Forgery (SSRF) flaw in the POST /api/v1/knowledge-bases/:id/knowledge/url endpoint. The vulnerable component fails to re-validate HTTP redirect targets after receiving a 3xx response when downloading documents from user-supplied URLs. An authenticated attacker can supply a public URL that initially passes SSRF validation, but redirects to internal network addresses (e.g., 127.0.0.1, private subnets) or cloud metadata endpoints (e.g., AWS IMDSv2). This allows attackers to access internal services and extract sensitive metadata despite initial validation. The issue affects WeKnora versions before 0.7.0; patches are available in 0.7.0 and later.

## Affected products

- Tencent WeKnora before 0.7.0

## Timeline

- 2026-09-15: disclosed: Published on NVD

## References

- [https://github.com/Tencent/WeKnora](https://github.com/Tencent/WeKnora)
- [https://github.com/Tencent/WeKnora/blob/v0.6.2/internal/application/service/knowledge_util.go](https://github.com/Tencent/WeKnora/blob/v0.6.2/internal/application/service/knowledge_util.go)

## Related threats

- [WeKnora server-side request forgery in isRestrictedIP()](https://junglewise.ai/threats/cve-2026-118376-weknora-before-0-8-2-contains-a-server-side-request-forgery)
- [Tencent WeKnora SQL injection in validateSubquery](https://junglewise.ai/threats/cve-2026-108821-a-security-vulnerability-has-been-detected-in-tencent-weknora-up)
- [Tencent WeKnora authorization bypass in Config API Endpoint](https://junglewise.ai/threats/cve-2026-8786-tencent-weknora-authorization-bypass-in-config-api-endpoint)
