# CVE-2026-47752: Tugtainer has Server-Side Template Injection in notification templates that leads to Remote Code Execution

> Authenticated users can execute arbitrary OS commands as root via Server-Side Template Injection in notification templates.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-g2cj-2x47-78vq

## What is CVE-2026-47752?

CVE-2026-47752 is a critical code injection vulnerability in Quenary tugtainer, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tugtainer is a self-hosted app for automating updates of Docker containers. Versions prior to 1.30.2 are vulnerable to Server-Side Template Injection (SSTI) in the notification template feature. The `title_template` and `body_template` fields are rendered using an unsandboxed `jinja2.Environment`, allowing any authenticated user to execute arbitrary OS commands as root inside the container. Version 1.30.2 fixes the issue.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-47752?


## How do I fix CVE-2026-47752?

No fix has been published for CVE-2026-47752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47752 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47752 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47752 and fix it if it is affected.

What it is: CVE-2026-47752 is a critical code injection vulnerability in Quenary tugtainer, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47752 exists.

Affected product: Quenary tugtainer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47752/ (Markdown: https://insights.sbomify.com/CVE-2026-47752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47752
- OSV: https://osv.dev/vulnerability/CVE-2026-47752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47752/
Summaries are generated and may contain mistakes; the official description above is the record.