TugtainerApplication · Quenary
CVE-2025-69201
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTugtainer 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTugtainer versions prior to 1.15.1 contain a command injection vulnerability in the tugtainer-agent's POST /api/command/run endpoint. Attackers can inject arbitrary arguments/commands that will be executed on the host system where the agent runs, leading to complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TugtainerApplication
< 1.15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Tugtainer versionRun the command to check the tugtainer-agent version, such as 'tugtainer-agent --version' or inspect the package metadata file if installed via a package managerAffected if The version number returned is less than 1.15.1 (for example, 1.15.0, 1.14.x, or earlier)
-
Verify the tugtainer-agent API is network accessibleCheck the network configuration or firewall rules to determine if the tugtainer-agent service port (typically the API port) is exposed to untrusted networks or the internetAffected if The API port is exposed to networks outside the trusted administrative network
-
Inspect API access logs for the vulnerable endpointReview the tugtainer-agent access logs for POST requests to /api/command/run, focusing on requests containing unusual or suspicious argument patternsAffected if Requests to /api/command/run contain unexpected characters, multiple command separators, or shell metacharacters in the arguments
-
Check for unauthorized command executionReview system audit logs, process accounting logs, or the tugtainer-agent execution logs for commands that were spawned by the agent but originated from API requestsAffected if There are command executions in the logs that do not correspond to legitimate administrative tasks
A user is affected if their installed Tugtainer version is below 1.15.1 AND the tugtainer-agent API is network-accessible to untrusted parties, or if evidence of exploitation is found in logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.15.1
Upgrade to Tugtainer version 1.15.1 or later. Until then, restrict network access to the tugtainer-agent API and monitor for suspicious API requests.
1.15.1
- Backup your tugtainer data and configuration before upgrading
- Upgrade tugtainer to version 1.15.1 using your installation method (e.g., docker pull, package manager, or binary)
- Restart the tugtainer service after upgrading
- Verify the upgrade was successful by checking the version number
- Test that the POST api/command/run endpoint properly sanitizes input and no longer allows command injection
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tugtainer
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data