Quick answers
- Is CVE-2026-102437 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102437 being exploited in the wild.
- How severe is CVE-2026-102437?
- High severity, with a CVSS score of 7.8, published 29 September 2026.
- Which products and versions are affected?
- Esengine DeepSeek-Reasonix <UNKNOWN>.
- Is there a fix for CVE-2026-102437?
- 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-102437 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-102437?
- Check whether you run Esengine DeepSeek-Reasonix 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 vulnerability is an OS command injection in the internal/gitcmd component triggered during git diff filter invocation (clean/smudge filters). A local attacker with write access to repository content can craft malicious .gitattributes and .git/config files to inject shell metacharacters into filter commands. The attack requires local access and user interaction (opening the diff viewer), but results in arbitrary command execution in the application's security context.
Affected products
- esengine DeepSeek-Reasonix <UNKNOWN>
Timeline
- 2026-09-29: disclosed