Quick answers
- Is CVE-2026-51883 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51883 being exploited in the wild.
- How severe is CVE-2026-51883?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Chatchat-Space Langchain-Chatchat 0.3.0, 0.3.1.
- Is there a fix for CVE-2026-51883?
- No fixed version is recorded yet. Restrict network access to the Langchain-Chatchat service and validate all `knowledge_base_name` inputs by rejecting names containing `../`, `..\ `, or absolute paths before path construction.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-51883 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51883?
- Check whether you run Chatchat-Space Langchain-Chatchat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Restrict network access to the Langchain-Chatchat service and validate all `knowledge_base_name` inputs by rejecting names containing `../`, `..\ `, or absolute paths before path construction.</anigation> </invoke>
Technical details
The vulnerability is a directory traversal flaw in the knowledge base creation and document upload interfaces. User-controlled input in the `knowledge_base_name` parameter is passed directly to file path construction without sanitization, validation, or boundary checks. An attacker can inject sequences like `..\ ` (Windows) or `../` (Unix) to write files outside the configured knowledge base root directory, achieving arbitrary file write on the host system.
Affected products
- Chatchat-space Langchain-Chatchat 0.3.0, 0.3.1
Timeline
- 2026-04-20: disclosed
- 2026-10-01: advisory