Skip to main content
CVE-2026-134755VulnerabilityPublished

better-chatbot before 2.0.0 contains a missing authorization vulnerability that lets built-in tools run without user

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134755· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 2.0.0 when convenient.

Data as of 22 Nov 2026, 16:25 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.0
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 2.0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 21 Nov 2026.

What to do

Upgrade better-chatbot to 2.0.0.

Affected software

ProductAffectedFixed in
keinsaasforeverbetter-chatbotAffected
  • <2.0.0
Fixed in
  • 2.0.0
GitHubbetter-chatbotpkg:github/better-chatbotOther threatsAffected
  • <2.0.0
Fixed in
  • 2.0.0

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

AI-suggested

If you cannot patch yet, avoid using vulnerable versions of better-chatbot in environments where untrusted input can be processed, and restrict access to Manual tool mode if possible.

Description

better-chatbot versions before 2.0.0 have a missing authorization vulnerability that allows built-in tools to execute without user confirmation in Manual tool mode. This occurs because the execute handlers for these tools remain active in the source file src/app/api/chat/route.ts. An attacker can exploit this by planting prompt-injected documents or web pages that cause the HTTP request tool to send conversation data to attacker-controlled URLs.

References

Community reviews

Loading reviews…