# CVE-2026-55181: Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false

> Attackers can initiate OIDC login flows in Tugtainer even when OIDC is disabled, bypassing the intended security configuration.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-rg7c-vpfp-2w43

## What is CVE-2026-55181?

CVE-2026-55181 is a critical vulnerability in Quenary tugtainer, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-55181?


## How do I fix CVE-2026-55181?

No fix has been published for CVE-2026-55181 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55181 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55181 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55181 and fix it if it is affected.

What it is: CVE-2026-55181 is a critical vulnerability in Quenary tugtainer, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55181 exists.

Affected product: Quenary tugtainer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55181/ (Markdown: https://insights.sbomify.com/CVE-2026-55181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55181
- OSV: https://osv.dev/vulnerability/CVE-2026-55181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55181/
Summaries are generated and may contain mistakes; the official description above is the record.