Loading vulnerability…
ChatterBot (<= 1.2.10) contains a denial-of-service vulnerability due to improper database session and SQLAlchemy connection pool lifecycle management. Under concurrent invocations of the get_response() method, database connections are not released promptly/appropriately, allowing the SQLAlchemy QueuePool to be exhausted. Once the pool is exhausted, subsequent requests cannot obtain a connection, leading to persistent service unavailability that typically requires a manual restart to recover. The issue is fixed in ChatterBot 1.2.11.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository purpose: a minimal proof-of-concept for CVE-2026-23842 (GHSA-v4w8-49pv-mf72), a high-severity DoS in ChatterBot <= 1.2.10 caused by database session/connection pool exhaustion under concurrent get_response() calls. Structure: - CVE-2026-23842.py: standalone Python PoC (entry point) that instantiates a ChatBot("dos-test") and spawns 30 threads; each thread calls bot.get_response("hello"). This concurrency can exhaust SQLAlchemy QueuePool resources, leading to sqlalchemy.exc.TimeoutError and application hang/unavailability. - README.md: detailed vulnerability write-up (affected/patched versions, root cause, CVSS vector, and the same PoC code). - LICENSE: MIT. Exploit capabilities: - Denial-of-service via uncontrolled resource consumption (CWE-400) by inducing concurrent get_response() execution. - No data exfiltration or code execution; no network scanner or targeting logic included. Fingerprintable endpoints/targets: - No hardcoded victim URLs/IPs/domains in code. The only explicit network URLs are GitHub user-attachments links in the README (image/video). The practical target is any ChatterBot deployment (<=1.2.10) that exposes get_response() behind a network-accessible API, where an attacker can generate sufficient concurrent requests to exhaust the DB connection pool.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.