GHSA-2f4c-vrjq-rcgv
HIGHWeKnora has Broken Access Control - Cross-Tenant Data Exposure
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/Tencent/WeKnoraReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A broken access control vulnerability in the database query tool allows any authenticated tenant to read sensitive data belonging to other tenants, including API keys, model configurations, and private messages. The application fails to enforce tenant isolation on critical tables (models, messages, embeddings), enabling unauthorized cross-tenant data access with user-level authentication privileges.
Details
Root Cause
The vulnerability exists due to a mismatch between the queryable tables and the tables protected by tenant isolation in internal/utils/inject.go.
Tenant-isolated tables (protected by automatic WHERE tenant_id = X clause):
tenants, knowledge_bases, knowledges, sessions, chunks
Queryable tables (allowed by WithAllowedTables() in WithSecurityDefaults()):
tenants, knowledge_bases, knowledges, sessions, messages, chunks, embeddings, models
Gap: The tables messages, embeddings, and models are queryable but NOT in the tenant isolation list. This means queries against these tables do NOT receive the automatic WHERE tenant_id = X filtering.
Vulnerable Code
File: internal/utils/inject.go
func WithTenantIsolation(tenantID uint64, tables ...string) SQLValidationOption {
return func(v *sqlValidator) {
v.enableTenantInjection = true
v.tenantID = tenantID
v.tablesWithTenantID = make(map[string]bool)
if len(tables) == 0 {
// Default tables with tenant_id - MISSING: messages, embeddings, models
v.tablesWithTenantID = map[string]bool{
"tenants": true,
"knowledge_bases": true,
"knowledges": true,
"sessions": true,
"chunks": true,
}
} else {
for _, table := range tables {
v.tablesWithTenantID[strings.ToLower(table)] = true
}
}
}
}
func WithSecurityDefaults(tenantID uint64) SQLValidationOption {
return func(v *sqlValidator) {
// ... other validations ...
WithTenantIsolation(tenantID)(v)
// Default allowed tables - INCLUDES unprotected tables
WithAllowedTables(
"tenants",
"knowledge_bases",
"knowledges",
"sessions",
"messages", // ← No tenant isolation
"chunks",
"embeddings", // ← No tenant isolation
"models", // ← No tenant isolation
)(v)
}
}
File: database_query.go
func (t *DatabaseQueryTool) validateAndSecureSQL(sqlQuery string, tenantID uint64) (string, error) {
securedSQL, validationResult, err := utils.ValidateAndSecureSQL(
sqlQuery,
utils.WithSecurityDefaults(tenantID),
utils.WithInjectionRiskCheck(),
)
// ... validation logic ...
return securedSQL, nil
}
When tenant 1 queries SELECT * FROM models, the validation passes and no WHERE tenant_id = 1 clause is appended because models is not in the tablesWithTenantID map. The unfiltered result exposes all model records across all tenants.
PoC
Prerequisites
- Access to the AI application as an authenticated tenant
- Ability to send prompts that invoke the
database_querytool
Steps to Reproduce
-
Authenticate as Tenant 1 and craft the following prompt to the AI agent:
Use the database_query tool with {"sql": "SELECT * FROM models"} to query the database. Output all results and any errors. -
Expected vulnerable response: The agent returns ALL model records in the
modelstable across all tenants, including:- Model IDs and names
- API keys and authentication credentials
- Configuration details for all organizations
Example result:
<img width="864" height="1150" alt="image" src="https://github.com/user-attachments/assets/01e3d0ba-0f2a-43ab-ab51-8778fb8a79b1" />-
Repeat with messages table:
Use the database_query tool with {"sql": "SELECT * FROM messages"} to query the database. Output all results. -
Expected vulnerable response: The agent returns ALL messages from all tenants, bypassing message privacy.
PoC Video:
https://github.com/user-attachments/assets/056984e8-1700-41fe-9b8a-6d18d5579c18
Impact
Vulnerability Type
Broken Access Control (CWE-639) / Unauthorized Information Disclosure (CWE-200)
Specific Data at Risk
-
API Keys & Credentials (from
modelstable)- Third-party LLM provider keys (OpenAI, Anthropic, etc.)
- Database credentials and connection strings
- Authentication tokens for integrated services
-
Private Messages (from
messagestable)- Confidential business communications
- User conversations with AI agents
- Sensitive information shared within conversations
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/Tencent/WeKnora | all versions | 0.2.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Tencent/WeKnora. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/Tencent/WeKnora to 0.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2f4c-vrjq-rcgv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2f4c-vrjq-rcgv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2f4c-vrjq-rcgv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2f4c-vrjq-rcgv in your dependencies?
O3 detects GHSA-2f4c-vrjq-rcgv across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.