chatterbot CVE Vulnerabilities & Metrics

Focus on chatterbot vulnerabilities and metrics.

Last updated: 15 Feb 2026, 23:25 UTC

About chatterbot Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with chatterbot. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total chatterbot CVEs: 1
Earliest CVE date: 19 Jan 2026, 19:16 UTC
Latest CVE date: 19 Jan 2026, 19:16 UTC

Latest CVE reference: CVE-2026-23842

Rolling Stats

30-day Count (Rolling): 1
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical chatterbot CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.0

Max CVSS: 0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 1
4.0-6.9 0
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS chatterbot CVEs

These are the five CVEs with the highest CVSS scores for chatterbot, sorted by severity first and recency.

All CVEs for chatterbot

CVE-2026-23842 chatterbot vulnerability CVSS: 0 19 Jan 2026, 19:16 UTC

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.