Categories
CVE-2026-58168 high CVSS 8.8

Vulnerability in deeptutor (CVE-2026-58168)

Summary

Vulnerability in deeptutor (CVE-2026-58168). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.4.10 or later.

Original description

The description as published by the source.

DeepTutor before version 1.4.10 contains an authorization bypass vulnerability that allows low-privilege users to invoke unrestricted MCP tools due to the allowed_mcp_tools function returning None instead of a denied result when mcp_tools is omitted from a user's grant in deeptutor/multi_user/tool_access.py. Attackers or prompt-injected content acting within a user session can enumerate and invoke any configured MCP tool, including filesystem, shell, and browser servers, gaining unauthorized access to sensitive deployment resources.

Source: GitHub Security Advisories (Global) 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-58168 has been found in deeptutor.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade deeptutor to 1.4.10 or later.
If unsure, ask your IT team or search "deeptutor CVE-2026-58168" on the vendor's site.

CVE-2026-58168 (deeptutor) — CWE-862 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.4.10 — 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-862) exists in deeptutor.

📍 Affected scope

Check the vendor advisory for the affected versions of deeptutor.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.4.10.

🛡️ 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 'deeptutor' . 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 'deeptutor' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade deeptutor to 1.4.10

    ステージング環境で 1.4.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

pip deeptutor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.10"}]}]
PyPI deeptutor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.10"}]}]

References

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