github.com/Tencent/WeKnora vulnerabilities
- Registry
- Go
- Latest
- 0.9.0
20 known advisories
The latest version, 0.9.0, is affected by 5 of them.
Is your project on an affected github.com/Tencent/WeKnora?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/Tencent/WeKnora
WeKnora is Vulnerable to SSRF via Redirection in github.com/Tencent/WeKnora
- Affected
- <0.2.12
- Fixed in
- 0.2.12
WeKnora has Broken Access Control - Cross-Tenant Data Exposure in github.com/Tencent/WeKnora
- Affected
- All versions
- Fixed in
- No fix released
WeKnora Vulnerable to Tool Execution Hijacking via Ambigous Naming Convention In MCP client and Indirect Prompt Injection in github.com/Tencent/WeKnora
- Affected
- All versions
- Fixed in
- No fix released
WeKnora has Unauthorized Cross‑Tenant Knowledge Base Cloning in github.com/Tencent/WeKnora
- Affected
- All versions
- Fixed in
- No fix released
WeKnora Vulnerable to Remote Code Execution via SQL Injection Bypass in AI Database Query Tool in github.com/Tencent/WeKnora
- Affected
- All versions
- Fixed in
- No fix released
WeKnora Vulnerable to Broken Access Control in Tenant Management in github.com/Tencent/WeKnora
- Affected
- <0.3.1
- Fixed in
- 0.3.1
WeKnora has DNS Rebinding Vulnerability in web_fetch Tool that Allows SSRF to Internal Resources in github.com/Tencent/WeKnora
- Affected
- All versions
- Fixed in
- No fix released
WeKnora has Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation in github.com/Tencent/WeKnora
- Affected
- >=0.2.6 <0.2.10
- Fixed in
- 0.2.10
WeKnora has Remote Code Execution (RCE) via Command Injection in MCP Stdio Configuration Validation
- Affected
- >=0.2.5 <0.2.10
- Fixed in
- 0.2.10
WeKnora Vulnerable to Remote Code Execution via SQL Injection Bypass in AI Database Query Tool
- Affected
- <0.2.12
- Fixed in
- 0.2.12
WeKnora has Broken Access Control - Cross-Tenant Data Exposure
- Affected
- <0.2.12
- Fixed in
- 0.2.12
WeKnora has DNS Rebinding Vulnerability in web_fetch Tool that Allows SSRF to Internal Resources
- Affected
- <0.3.0
- Fixed in
- 0.3.0
WeKnora has Unauthorized Cross‑Tenant Knowledge Base Cloning
- Affected
- <0.3.0
- Fixed in
- 0.3.0
WeKnora Vulnerable to Tool Execution Hijacking via Ambigous Naming Convention In MCP client and Indirect Prompt Injection
- Affected
- <0.3.0
- Fixed in
- 0.3.0
WeKnora Vulnerable to Broken Access Control in Tenant Management
- Affected
- <0.3.2
- Fixed in
- 0.3.2
WeKnora is Vulnerable to SSRF via Redirection
- Affected
- <0.2.12
- Fixed in
- 0.2.12
WeKnora has Command Injection in MCP stdio test in github.com/Tencent/WeKnora
- Affected
- <0.2.5
- Fixed in
- 0.2.5
WeKnora vulnerable to SQL Injection in github.com/Tencent/WeKnora
- Affected
- <0.2.5
- Fixed in
- 0.2.5
WeKnora has Command Injection in MCP stdio test
- Affected
- <0.2.5
- Fixed in
- 0.2.5
WeKnora vulnerable to SQL Injection
- Affected
- <0.2.5
- Fixed in
- 0.2.5
Is your github.com/Tencent/WeKnora version vulnerable?
- github.com/Tencent/WeKnora 0.95 advisories in 0.9.0
- github.com/Tencent/WeKnora 0.85 advisories in 0.8.3
- github.com/Tencent/WeKnora 0.75 advisories in 0.7.2
- github.com/Tencent/WeKnora 0.65 advisories in 0.6.3
- github.com/Tencent/WeKnora 0.55 advisories in 0.5.2
- github.com/Tencent/WeKnora 0.45 advisories in 0.4.0
Which of your client projects still run an old github.com/Tencent/WeKnora?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.