Categories
CVE-2026-58198 medium CVSS 5.5

Vulnerability in chatterbot (CVE-2026-58198)

Summary

Vulnerability in chatterbot (CVE-2026-58198). Confidential information can be exposed externally. Exploitable via makedirs. Mitigation: upgrade to 1.2.14 or later.

Original description

The description as published by the source.

ChatterBot is a machine learning, conversational dialog engine for creating chat bots. Prior to 1.2.14, UbuntuCorpusTrainer.extract() uses a predictable home-rooted output directory (~/ubuntu_data/ubuntu_dialogs) with a check-then-create pattern followed by tar.extractall(path=self.data_path), allowing a local attacker who pre-plants a symlink at the predictable path to cause archive contents to be written through the symlink to an attacker-chosen directory. This issue is fixed in version 1.2.14.

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-58198 has been found in chatterbot.
Attackers can target a specific entry point like makedirs over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade chatterbot to 1.2.14 or later.
If unsure, ask your IT team or search "chatterbot CVE-2026-58198" on the vendor's site.

CVE-2026-58198 (chatterbot) — CWE-367 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: makedirs / extractall / safe_extract / self.data_path
Patched: 1.2.14 — 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-367) exists in chatterbot. Attackers reach the vulnerable code path via makedirs.

📍 Affected scope

Check the vendor advisory for the affected versions of chatterbot. Attack surface: makedirs / extractall / safe_extract / self.data_path.

🔥 Severity

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

🔧 How to fix

Update to 1.2.14.

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

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

  2. 2
    Apply patch patch
    Upgrade chatterbot to 1.2.14

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

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

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

Affected packages

PyPI chatterbot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.14"}]}]

References

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