Skip to main content
CVE-2026-23842VulnerabilityPublished Updated

CVE-2026-23842: gunthercox ChatterBot · Uncontrolled Resource Consumption

Affects gunthercox ChatterBotSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 1.2.11 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade ChatterBot and chatterbot to 1.2.11.

Affected software

ProductAffectedFixed in
gunthercoxChatterBotAffected
  • <1.2.11
Fixed in
  • 1.2.11
PyPIchatterbotpkg:pypi/chatterbotOther threatsAffected
  • <1.2.11
Fixed in
  • 1.2.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade all instances of gunthercox ChatterBot to version 1.2.11 or later, which includes fixes for proper database session and connection pool management. Organizations should audit their chatbot deployments to identify vulnerable versions and prioritize patching. Additionally, implement monitoring and alerting on database connection pool metrics to detect abnormal exhaustion patterns early. Rate limiting or throttling concurrent requests to the get_response() method can reduce the risk of resource exhaustion. Employing circuit breakers or fallback mechanisms in chatbot services can help maintain partial functionality during high load or attack conditions. Finally, ensure that deployment environments have robust logging to facilitate incident response and root cause analysis if service disruptions occur.

Description

ChatterBot is a machine learning, conversational dialog engine for creating chat bots. ChatterBot 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. Version 1.2.11 fixes the issue.

References

Community reviews

Loading reviews…