CVE-2025-69201: Quenary tugtainer · Command Injection
Affects Quenary tugtainerSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.15.1 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.15.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 29 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade quenary/tugtainer to 1.15.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubquenary/tugtainerpkg:github/quenary/tugtainerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all tugtainer instances to version 1.15.1 or later, which contains the fix for this command injection vulnerability. Until upgrades are completed, it is advisable to restrict network access to the tugtainer-agent API endpoint (POST api/command/run) using firewalls or network segmentation to limit exposure to trusted hosts only. Implement strict input validation and sanitization on any custom integrations interacting with tugtainer APIs to reduce injection risks. Monitor logs and network traffic for unusual command execution patterns or unexpected API calls that could indicate exploitation attempts. Employ container security best practices such as running tugtainer-agent with the least privileges necessary and isolating container management hosts from general user networks. Regularly audit and update container orchestration tools and dependencies to ensure timely application of security patches. Finally, incorporate tugtainer vulnerability scanning into vulnerability management programs to detect outdated versions proactively.
Description
Tugtainer is a self-hosted app for automating updates of docker containers. In versions prior to 1.15.1, arbitary arguments can be injected in tugtainer-agent `POST api/command/run`. Version 1.15.1 fixes the issue.
References
- github.com/Quenary/tugtainer/security/advisories/GHSA-grc3-8w5x-g54q (opens in a new tab)
- github.com/Quenary/tugtainer/pull/88 (opens in a new tab)
- github.com/Quenary/tugtainer/commit/dbb17d843e30fd7509acf0328c913dcb42f40831 (opens in a new tab)
- github.com/Quenary/tugtainer/releases/tag/v1.15.1 (opens in a new tab)