# CVE-2026-55181: Tugtainer OIDC authentication bypass when disabled

Source: https://junglewise.ai/threats/cve-2026-55181-tugtainer-is-a-self-hosted-app-for-automating-updates-of-docker  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-30. Updated: 2026-09-30  
License: CC BY 4.0 with a link back

CVE-2026-55181 · Severity: critical · CVSS 9.4 · Published 2026-09-30

Tugtainer is a self-hosted application that automates Docker container updates. When OIDC (OpenID Connect) authentication is disabled via configuration, attackers can still bypass this setting and initiate an OIDC login flow by directly accessing the login endpoint, potentially gaining unauthorized access to the system.

Technologies: [Quenary Tugtainer](https://junglewise.ai/threats/technologies/tugtainer). Vendors: [Quenary](https://junglewise.ai/threats/vendors/quenary).

## Quick answers

**Is CVE-2026-55181 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55181 being exploited in the wild.

**How severe is CVE-2026-55181?** Critical severity, with a CVSS score of 9.4, published 30 September 2026.

**Which products and versions are affected?** Quenary Tugtainer before 1.30.3.

**Is there a fix for CVE-2026-55181?** A patch was published on 2026-06-11: fix released in version 1.30.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-55181 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-55181?** Check whether you run Quenary Tugtainer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an authentication bypass in Tugtainer's OIDC provider that fails to check whether OIDC is enabled before processing login requests. While the /auth/oidc/enabled endpoint correctly reports OIDC as disabled, a direct request to /auth/oidc/login still initiates the OIDC flow and redirects to the configured authorization endpoint, circumventing the OIDC_ENABLED=false configuration switch. The issue has been patched in version 1.30.3 by adding enable checks in the auth provider classes.

## Affected products

- Quenary Tugtainer before 1.30.3

## Timeline

- 2026-09-30: disclosed
- 2026-06-11: patched: fix released in version 1.30.3

## References

- [https://github.com/Quenary/tugtainer/commit/76371db679334b002d4af544b0f3b8587ad86f52](https://github.com/Quenary/tugtainer/commit/76371db679334b002d4af544b0f3b8587ad86f52)
- [https://github.com/Quenary/tugtainer/releases/tag/v1.30.3](https://github.com/Quenary/tugtainer/releases/tag/v1.30.3)

## Related threats

- [Tugtainer OIDC ID token signature verification bypass](https://junglewise.ai/threats/cve-2026-87004-tugtainer-is-a-self-hosted-app-for-automating-updates-of-docker)
- [Tugtainer server-side request forgery in notification test endpoint](https://junglewise.ai/threats/cve-2026-62308-tugtainer-is-a-self-hosted-app-for-automating-updates-of-docker)
- [Tugtainer Agent authentication bypass when AGENT_SECRET not configured](https://junglewise.ai/threats/cve-2026-55494-tugtainer-is-a-self-hosted-app-for-automating-updates-of-docker)
- [Quenary Tugtainer SSTI in notification templates](https://junglewise.ai/threats/cve-2026-47752-quenary-tugtainer-ssti-in-notification-templates)
- [Tugtainer is a self-hosted app for automating updates of docker containers. In versions prior to 1.15.1, arbitary…](https://junglewise.ai/threats/cve-2025-69201-tugtainer-is-a-self-hosted-app-for-automating-updates-of-docker)