Key points
- CVE-2026-111704 is rated critical with a CVSS score of 9.3.
- Attackers can access REST controllers due to a missing Sa-Token interceptor.
- Exploitation allows reading plaintext passwords and retrieving LLM provider API keys.
LangChat installations through commit 2a6285a are affected by a critical authentication failure. The vendor has not yet confirmed the availability of a patch or update for this vulnerability. Administrators must verify their current version against this commit identifier to determine if their systems are exposed to unauthenticated remote attacks.
In plain English
The flaw exists because the application fails to register a necessary security interceptor called Sa-Token. This omission leaves REST API endpoints open to anyone on the internet. Without proper authentication checks, attackers do not need valid user credentials to interact with sensitive parts of the system. They can send requests directly to these unprotected endpoints.
The background
The National Vulnerability Database lists this issue as CVE-2026-111704. It is classified under CWE-306, which covers missing authentication for critical functions. The severity rating of 9.3 indicates a critical risk level. This classification reflects the ease with which an attacker can exploit the missing controls and the high impact of the resulting unauthorized access.
What changes now
Attackers can query the /api/v1/auth/users endpoint to view user passwords in plaintext. They can also retrieve API keys used for large language model providers. Furthermore, the vulnerability allows the creation of super-administrator accounts. Attackers may also modify or delete existing data within the application. No fix has been confirmed yet by the developers.
Who needs to act first
Teams should prioritize identifying any publicly accessible LangChat instances immediately. Check whether these systems are reachable from the internet without additional network controls. Isolate affected servers from external traffic if possible to prevent unauthorized access. Review access logs for suspicious activity around authentication endpoints. Prepare to apply a vendor update as soon as it becomes available. Test the patch in a non-production environment first.
What to do and how to stay safe: LangChat
- Verify if your LangChat version is at or before commit 2a6285a.
- Restrict network access to the application to trusted internal IPs only.
- Monitor logs for unusual requests to the /api/v1/auth/users endpoint.
- Wait for an official vendor patch before restoring full public access.
Step-by-step guide: Emergency Patching: How to Fix Critical Flaws Without Breaking Systems
General security guidance from the Patch Review newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-111704?
The CVSS score is 9.3, which is rated as critical.
Can attackers create admin accounts with this flaw?
Yes, unauthenticated attackers can create super-admin accounts.
Is there a patch available for this vulnerability?
No, the source material does not confirm that a fix exists.
