ChatterBot
ChatterBot is a machine learning, conversational dialog engine for creating chat bots
Activity
- Latest release
- 3w ago
- Total releases
- 96
- Cadence
- ~12 days
- Last 12 months
- 8
Reach
- Stars
- 14.5k
Details
- License
- BSD-3-Clause
- First release
- Oct 12, 2014
| Version | Released | |
|---|---|---|
1.2.15
patch
| ||
1.2.14
patch
| ||
1.2.13
patch
1 CVE
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.12
patch
1 CVE
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.11
patch
1 CVE
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.10
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.9
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.8
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.7
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.6
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.5
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.4
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.3
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.2
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.1
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.2.0
minor
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.8
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.7
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.1.0a7
pre
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.1.0
minor
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.5
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.4
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.3
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.2
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.1
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.0
major
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.0a4
pre
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.0a3
pre
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.0a2
pre
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
1.0.0a1
pre
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.7
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.6
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.5
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.4
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.3
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.2
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.1
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.8.0
minor
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.6
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.5
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.4
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.3
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.2
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.1
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.7.0
minor
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.6.3
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.6.2
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.6.1
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.6.0
minor
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev | ||
0.5.5
patch
2 CVEs
CVE-2026-23842
PYSEC-2026-1244
GHSA-v4w8-49pv-mf72
Jul 07, 2026
ChatterBot Vulnerable to Denial of Service via Database Connection Pool Exhaustion
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryChatterBot versions up to 1.2.10 are vulnerable to a denial-of-service condition caused by improper database session and connection pool management. Concurrent invocations of the get_response() method can exhaust the underlying SQLAlchemy connection pool, resulting in persistent service unavailability and requiring a manual restart to recover. DetailsChatterBot relies on SQLAlchemy for database access and uses a connection pool with default limits. The get_response() method does not enforce concurrency limits, rate limiting, or explicit session lifecycle controls. When multiple threads concurrently invoke get_response(), database connections are rapidly consumed and not released in a timely manner. This leads to exhaustion of the SQLAlchemy QueuePool, causing subsequent requests to block and eventually fail with a TimeoutError. This issue can be triggered without authentication in deployments where ChatterBot is exposed as a chatbot service, making it exploitable by remote attackers to cause denial of service. PoC Video: https://github.com/user-attachments/assets/4ee845c4-b847-4854-84ec-4b2fb2f7090f PoC
from chatterbot import ChatBot import threading bot = ChatBot("dos-test") def attack(): bot.get_response("hello") threads = [] for _ in range(30): t = threading.Thread(target=attack) t.start() threads.append(t) for t in threads: t.join()
ImpactThis vulnerability allows an attacker to trigger a denial-of-service condition by exhausting the database connection pool. Once triggered, the chatbot becomes unresponsive to legitimate users and requires a manual restart to restore functionality. All deployments of ChatterBot version 1.2.10 or earlier that allow concurrent access to the get_response() method are impacted. Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 79 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.11
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2026-58198
GHSA-wvrh-2f4m-924v
Jun 19, 2026
ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
High
None
None
SummaryChatterBot's The existing Vulnerability DetailsPredictable output directory (line 535-546)
Check-then-create (line 621-622)
Extraction through symlink (line 633-644)
Proof of ConceptEnvironment| Component | Detail | |-----------|--------| | chatterbot | 1.2.13 (pip install) | | Python | 3.11.0 | Exploit
PoC outputSuggested FixRefuse symlinks on the output directory before extraction:
Affected versions
0.0.0
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.1.0
0.1.1
0.1.2
0.2.0
0.2.1
0.2.2
+ 82 more Show less
0.2.3
0.2.4
0.2.5
0.2.6
0.2.7
0.2.8
0.2.9
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.3.5
0.3.6
0.3.7
0.4.0
0.4.1
0.4.10
0.4.11
0.4.12
0.4.13
0.4.2
0.4.3
0.4.4
0.4.5
0.4.6
0.4.7
0.4.8
0.4.9
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.6.0
0.6.1
0.6.2
0.6.3
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
1.0.0
1.0.0a1
1.0.0a2
1.0.0a3
1.0.0a4
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.7
1.0.8
1.1.0
1.1.0a7
1.2.0
1.2.1
1.2.10
1.2.11
1.2.12
1.2.13
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
1.2.8
1.2.9
Fixed in
1.2.14
References Updated Jul 10, 2026 · Source: OSV.dev |