Quick answers
- Is CVE-2026-51873 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51873 being exploited in the wild.
- How severe is CVE-2026-51873?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Stitionai Devika v1.0.
- Is there a fix for CVE-2026-51873?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. 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-51873 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51873?
- Check whether you run Stitionai Devika 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.
Technical details
The Coder.save_code_to_project function in src/agents/coder/coder.py accepts LLM-generated file paths without path normalization or boundary validation, then passes them directly to file write operations. An attacker can inject path traversal sequences (e.g., ../../) via Socket.IO messages to write files outside the project directory. The vulnerability is reachable through the Socket.IO user-message event and requires only the ability to communicate with the Devika server.
Affected products
- stitionai Devika v1.0
Timeline
- 2026-04-20: disclosed
- 2026-10-01: advisory