Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-91750 medium CVSS 6.5

SSRF (Server-Side Request Forgery) in WeKnora (CVE-2026-91750)

Summary

SSRF in WeKnora (CVE-2026-91750). Confidential information can be exposed externally. Exploitable via POST /api/v1/knowledge-bases/.

Original description

The description as published by the source.

WeKnora before 0.7.0 fails to re-validate HTTP redirect targets in the POST /api/v1/knowledge-bases/:id/knowledge/url endpoint when downloading documents from user-supplied URLs. Authenticated attackers can bypass initial SSRF validation by supplying a public URL that redirects to internal network addresses, allowing access to internal services and cloud metadata.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-91750 has been found in WeKnora.
Attackers can target a specific entry point like POST /api/v1/knowledge-bases/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WeKnora CVE-2026-91750" on the vendor's site.

CVE-2026-91750 (WeKnora) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/knowledge-bases/
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

SSRF (CWE-918) exists in WeKnora. Attackers reach the vulnerable code path via POST /api/v1/knowledge-bases/.

📍 Affected scope

Check the vendor advisory for the affected versions of WeKnora. Attack surface: POST /api/v1/knowledge-bases/.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 POST /api/v1/knowledge-bases/ requests with malformed payloads or SQL meta-characters. Run grep -r 'WeKnora' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'WeKnora' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で WeKnora を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/v1/knowledge-bases/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/knowledge-bases/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /api/v1/knowledge-bases/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details