CVE-2026-90938
Last modified
CVE-2026-90938 is a high-severity vulnerability rated 8.6/10 on the CVSS scale. LangBot's plugin runtime (pip package langbot_plugin) through 0.4.17 starts a debug WebSocket server on 0.0.0.0:5401 (/plugin/ws) whose authentication is gated on plugin_debug_key, which defaults to an empty string and is never set by the upstream repository, Docker image, or docker-compose (which additionally publishes port 5401 to the host); the key check is therefore skipped entirely. Any remote attacker able to reach the port can register an arbitrary "debug plugin" without credentials.
Description
LangBot's plugin runtime (pip package langbot_plugin) through 0.4.17 starts a debug WebSocket server on 0.0.0.0:5401 (/plugin/ws) whose authentication is gated on plugin_debug_key, which defaults to an empty string and is never set by the upstream repository, Docker image, or docker-compose (which additionally publishes port 5401 to the host); the key check is therefore skipped entirely. Any remote attacker able to reach the port can register an arbitrary "debug plugin" without credentials. Because events are broadcast to all initialized plugins without filtering, the attacker's plugin receives the full context of every IM message event (including private chats, message chains, and user/sender IDs in plaintext) and can inject forged replies, send messages as any configured bot, enumerate bot UUIDs, invoke configured LLM models, read knowledge-base contents, and register malicious tools that feed every user's LLM pipeline. Registering with "prod_mode": true causes later legitimate installations of a plugin with the same author/name to be rejected, resulting in persistent denial of service. No patched version was available at the time of publication.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| langbot-app | LangBot | <= 0.4.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90938?
How severe is CVE-2026-90938?
How do I fix CVE-2026-90938?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90932LaraDashboard versions 0.9.2 through 1.2.2 contain a path tr…7.2
- CVE-2026-90933laradashboard through 1.2.2 contains a missing authorization…7.1
- CVE-2026-90934EspoCRM before 10.0.4 contains a field-level security bypass…4.3
- CVE-2026-90935Froxlor before 2.3.7 fails to validate the mysql_server para…4.3
- CVE-2026-90936Froxlor before 2.3.7 fails to properly scope sender alias lo…4.3
- CVE-2026-90937froxlor versions before 2.2.5 fail to validate newline chara…9.9
- CVE-2026-90939novel-plus through 5.3.3 contains an information disclosure …6.5
- CVE-2026-9094Casdoor versions 2.362.0 and earlier contain a vulnerability…9.8
- CVE-2026-90940novel-plus through 5.3.3 contains an insecure default cache-…5.3
- CVE-2026-90941novel-plus through 5.3.3 contains an authorization bypass vu…4.3
- CVE-2026-90942Casdoor through 4.4.0 fails to properly mask the instance-wi…9.6
- CVE-2026-90943parallax filament-comments through 3.0.0 contains a stored c…8.7
Are you affected by CVE-2026-90938?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
