{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55181 exists.","fix":"No fix has been published for CVE-2026-55181 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-55181 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55181 exists.\n\nAffected product: Quenary tugtainer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55181/ (Markdown: https://insights.sbomify.com/CVE-2026-55181/index.md)","id":"CVE-2026-55181","markdown":"https://insights.sbomify.com/CVE-2026-55181/index.md","name":"CVE-2026-55181","record":{"aliases":["GHSA-rg7c-vpfp-2w43"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker container updater","requires_auth":"none","summary":"Attackers can initiate OIDC login flows in Tugtainer even when OIDC is disabled, bypassing the intended security configuration.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false","id":"CVE-2026-55181","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"LibreNMS: Remote Code Execution by Signal Alert Transportation Module","id":"CVE-2026-55182"},"packages":[],"prev":{"headline":"pnpm: Repository config can expand victim environment secrets into registry requests before scripts run","id":"CVE-2026-55180"},"products":["tugtainer"],"published":"2026-09-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Quenary"]},"summary":"Attackers can initiate OIDC login flows in Tugtainer even when OIDC is disabled, bypassing the intended security configuration.","url":"https://insights.sbomify.com/CVE-2026-55181/"}