{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-87004 exists.","fix":"No fix has been published for CVE-2026-87004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-87004 is a high-severity authentication bypass 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-87004 and fix it if it is affected.\n\nWhat it is: CVE-2026-87004 is a high-severity authentication bypass 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-87004 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-87004/ (Markdown: https://insights.sbomify.com/CVE-2026-87004/index.md)","id":"CVE-2026-87004","markdown":"https://insights.sbomify.com/CVE-2026-87004/index.md","name":"CVE-2026-87004","record":{"aliases":["GHSA-crjc-6vc7-xrfh"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker container updater","requires_auth":"none","summary":"Attackers can bypass OIDC authentication in Tugtainer by forging unsigned id_tokens, gaining unauthorized access to the container automation platform.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.31.3, when the OIDC login flow completes, backend/modules/auth/providers/auth_oidc_provider.py decodes the id_token returned by the identity provider's token endpoint using jose.jwt.get_unverified_claims() instead of jwt.decode(). This skips signature verification, audience (aud) validation, issuer (iss) validation, and expiry (exp) checking entirely. The extracted claims (email/sub/preferred_username) are then used directly as the user_id for the resulting Tugtainer session. This issue has been patched in version 1.31.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-03T07:47:42Z","kind":"github_poc","ref":"https://github.com/squeeze440/tugtainer-PoC","stars":0,"title":"PoC — OIDC id_token accepted without signature/audience/expiry check in Tugtainer (GHSA-crjc-6vc7-xrfh, CVE-2026-87004, CVSS 8.1)."}],"tier":"weaponised"},"has_fix":false,"headline":"Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification","id":"CVE-2026-87004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout","id":"CVE-2026-87011"},"packages":[],"prev":{"headline":"n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy","id":"CVE-2026-86996"},"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Quenary"]},"summary":"Attackers can bypass OIDC authentication in Tugtainer by forging unsigned id_tokens, gaining unauthorized access to the container automation platform.","url":"https://insights.sbomify.com/CVE-2026-87004/"}