OIDC disable bypass via unawaited enablement check
Published Sep 30, 2026 · Updated Sep 30, 2026
Authentication bypass in Quenary Tugtainer before 1.30.3 allows remote attackers to initiate OIDC login despite OIDC_ENABLED=false. The login method in auth_oidc_provider.py calls the asynchronous is_enabled() check without awaiting it, so the check evaluates a coroutine rather than the disabled state. The demonstrated result is an OIDC redirect; obtaining an application session additionally requires a configured identity provider and valid credentials.
Summary
What happened
Authentication bypass in Quenary Tugtainer before 1.30.3 allows remote attackers to initiate OIDC login despite OIDC_ENABLED=false. The login method in auth_oidc_provider.py calls the asynchronous is_enabled() check without awaiting it, so the check evaluates a coroutine rather than the disabled state. The demonstrated result is an OIDC redirect; obtaining an application session additionally requires a configured identity provider and valid credentials.
The record
- CVE
- CVE-2026-55181
- Published
- Sep 30, 2026
- Updated
- Sep 30, 2026
- Vendor
- Quenary
- Product
- Tugtainer
- Classifications
- T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2026CVE publishedPublication date reported by the CVE source.
- Sep 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.30.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Vendor-advisory OIDC login reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started