CVE-2026-55494: Quenary tugtainer · Improper Access Control
Affects Quenary tugtainerSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.30.4 as a priority.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.30.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade Quenary tugtainer to 1.30.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Quenarytugtainer | Affected
| Fixed in
|
PyPItugtainerpkg:pypi/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
Upgrade Tugtainer to version 1.30.4 or later, where this vulnerability is patched. Ensure that AGENT_SECRET is properly configured to enable signature verification and protect API routes. No additional mitigations are necessary once the patch is applied.
Description
Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.30.4, Tugtainer Agent allows unauthenticated access to Docker management APIs when AGENT_SECRET is not configured. The Agent uses request signatures to protect its API routes. However, in agent/auth.py, the signature verification function returns successfully if Config.AGENT_SECRET is empty. This causes protected Agent APIs to become accessible without authentication. This issue has been patched in version 1.30.4.