Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55494 – Authentication Bypass (Unauthenticated Docker API Access) – Tugtainer Agent ≤ 1.30.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-55494 is a critical (CVSS 9.8) improper access control vulnerability in the Tugtainer Agent, a self-hosted tool used to automate updates of Docker containers. When the agent’s AGENT_SECRET environment variable is left unconfigured, its request-signature verification logic silently skips authentication, allowing unauthenticated network attackers to reach privileged Docker management APIs. Public proof-of-concept exploit code is available, including a chain combining this flaw with a second vulnerability (CVE-2026-62308) to achieve root-level remote code execution on the host.

Technical details

  • Root cause: the verify_signature() function in the agent’s auth.py returns success and exits before performing any credential check when Config.AGENT_SECRET is empty or unset.
  • Trigger condition: any deployment of Tugtainer Agent that does not have AGENT_SECRET explicitly configured is left with its signature verification effectively disabled.
  • Attack vector: network-based, no authentication or user interaction required (CVSS AV:N, PR:N, UI:N).
  • Impact: unauthenticated access to Docker management endpoints — listing, inspecting, creating, starting, stopping, and removing containers, pulling/pruning images, and reading container logs/environment variables. Published exploit chains further leverage this access, combined with CVE-2026-62308, to spawn a container sharing the host’s PID namespace, gaining filesystem access via /proc/1/root and resulting in root-level remote code execution on the underlying host.

Affected software

  • Quenary Tugtainer Agent versions prior to 1.30.4 (confirmed vulnerable in versions including 1.30.2).
  • Fixed in version 1.30.4.

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade Tugtainer Agent to version 1.30.4 or later, which requires AGENT_SECRET to be configured by default and requires an explicit override flag to run without authentication.
  • If immediate patching is not possible: ensure AGENT_SECRET is set to a strong, randomly generated value on every deployment, and restrict network access to the Tugtainer Agent’s API endpoints (e.g., via firewall rules or placing the service on an internal-only network) so it is not reachable from the internet or untrusted networks.
  • Review Docker socket permissions granted to the Tugtainer Agent, as the severity of exploitation depends on the privileges available to containers it manages.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge