CVE-2026-55181: falha crítica em Quenary tugtainer
Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false
Publicada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
28Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 9.4epss 0.6%
Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.30.3, Tugtainer's OIDC authentication can still be initiated even when OIDC_ENABLED=false. The /auth/oidc/enabled endpoint correctly reports that OIDC is disabled. However, a direct request to /auth/oidc/login still starts the OIDC login flow, returns HTTP 302, sets an oidc_state cookie, and redirects the user to the configured OIDC authorization endpoint. This bypasses the intended OIDC disable switch. This issue has been patched in version 1.30.3.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Produtos afetados
Quenary · tugtainerCVEs relacionadas — Quenary tugtainer
No mesmo produto, das mais perigosas para as menos.
CVE-2026-55494CRITICALTugtainer: Unauthenticated access to Tugtainer Agent Docker management APIs when AGENT_SECRET is unsetEPSS 0.6%CVE-2026-23846HIGHTugtainer vulnerable to Password Exposure via URL Query ParameterEPSS 0.5%CVE-2025-69201HIGHTugtainer has RCE in Agent Command Execution ApiEPSS 0.5%CVE-2026-47752CRITICALTugtainer has Server-Side Template Injection in notification templates that leads to Remote Code ExecutionEPSS 0.4%CVE-2026-62308CRITICALTugtainer: Authenticated SSRF via arbitrary notification URLs in test_notification endpointEPSS 0.3%CVE-2026-87004HIGHTugtainer: OIDC id_token claims accepted without signature/audience/expiry verificationEPSS 0.3%