Quick answers
- Is CVE-2026-47752 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47752 being exploited in the wild.
- How severe is CVE-2026-47752?
- Critical severity, with a CVSS score of 9.9, published 23 July 2026.
- Which products and versions are affected?
- Quenary Tugtainer < 1.30.2.
- Is there a fix for CVE-2026-47752?
- A patch was published on 2026-07-23: Version 1.30.2 released to address the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47752 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47752?
- Check whether you run Quenary Tugtainer 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
Tugtainer versions prior to 1.30.2 are vulnerable to Server-Side Template Injection (SSTI) within the notification template feature. The root cause is the use of an unsandboxed `jinja2.Environment` in `backend/core/notifications_core.py` to render the `title_template` and `body_template` fields. An authenticated attacker can submit malicious Jinja2 expressions via the `/api/settings/test_notification` endpoint to escape the template environment and access Python built-ins. This allows for Remote Code Execution (RCE) as the root user within the container. Because the application often has access to the Docker socket, an attacker could potentially compromise the entire host or other containers. The issue is resolved in version 1.30.2 by migrating to `jinja2.sandbox.SandboxedEnvironment`.
Affected products
- Quenary Tugtainer < 1.30.2
Timeline
- 2026-05-20: advisory: Original GitHub security advisory published
- 2026-07-23: disclosed: CVE published to NVD
- 2026-07-23: patched: Version 1.30.2 released to address the vulnerability