Quick answers
- Is CVE-2025-27770 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-27770 being exploited in the wild.
- How severe is CVE-2025-27770?
- Informational severity, with a CVSS score of 8.2, published 17 August 2026.
- Which products and versions are affected?
- UpTrain 0.7.1 and prior.
- Is there a fix for CVE-2025-27770?
- 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-2025-27770 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-27770?
- Check whether you run UpTrain 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 a code injection flaw in the `/create_project` endpoint of UpTrain versions 0.7.1 and prior. The endpoint passes user-supplied `checks` and `metadata` parameters directly to Python's `eval()` function without sanitization, enabling arbitrary code execution. An attacker must have access to UpTrain and a valid authentication method (such as the default static API key). The vulnerable code uses `checks = eval(checks[0])` and `metadata = eval(metadata)`, allowing an attacker to inject malicious Python code that executes in the context of the UpTrain host process. As of publication, no patch is available; the project appears to be unmaintained as of March 2025.
Affected products
- UpTrain UpTrain 0.7.1 and prior
Timeline
- 2026-08-17: disclosed: CVE-2025-27770 published on NVD
- 2024-09-05: other: Issue opened in repo with no response from maintainers
- 2025-03-10: other: Slack messages indicate project is no longer being maintained
- 2026-08-10: other: Pull request opened with fix in repo