← Back
CVE-2026-11500
medium
CVSS 5.0
Vulnerability in github.com/weaviate/weaviate (CVE-2026-11500)
Summary
vulnerability in github.com/weaviate/weaviate (CVE-2026-11500). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.38.0-rc.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-11500** has been found in github.com/weaviate/weaviate.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade github.com/weaviate/weaviate to **1.38.0-rc.0** or later.
If unsure, ask your IT team or search "github.com/weaviate/weaviate CVE-2026-11500" on the vendor's site.
CVE-2026-11500 (github.com/weaviate/weaviate) — CWE-285 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Patched: `1.38.0-rc.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-285) exists in github.com/weaviate/weaviate.
📍 Affected scope
github.com/weaviate/weaviate — .
🔥 Severity
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.38.0-rc.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/weaviate/weaviate' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/weaviate/weaviate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/weaviate/weaviate` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/weaviate/weaviate to 1.38.0-rc.0ステージング環境で 1.38.0-rc.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/weaviate/weaviate
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.38.0-rc.0"}]}]
References
- web [email protected]
- web https://github.com/weaviate/weaviate/commit/40f2cc32279f0f8a51016c3c6870a2c0c808e6c0
- web https://github.com/weaviate/weaviate/issues/11392
- web https://github.com/weaviate/weaviate/releases/tag/v1.38.0-rc.0
- web https://vuldb.com/cve/CVE-2026-11500
- web https://vuldb.com/submit/835080
- web https://vuldb.com/vuln/369120
- web https://vuldb.com/vuln/369120/cti
- web https://nvd.nist.gov/vuln/detail/CVE-2026-11500
- web https://github.com/weaviate/weaviate
- web https://github.com/advisories/GHSA-jqpm-wf57-qx5c