Skip to main content
VulnerabilityPublished

CVE-2026-55181: Quenary tugtainer · Improper Access Control

Affects Quenary tugtainerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical : upgrade to 1.30.3 as a priority.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.30.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade tugtainer and quenary/tugtainer to 1.30.3.

Affected software

ProductAffectedFixed in
QuenarytugtainerAffected
  • <1.30.3
Fixed in
  • 1.30.3
GitHubquenary/tugtainerpkg:github/quenary/tugtainerOther threatsAffected
  • <1.30.3
Fixed in
  • 1.30.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Tugtainer to version 1.30.3 or later, where this issue is patched. No other mitigation is required as the fix addresses the improper access control allowing OIDC login flow initiation when disabled.

Description

Tugtainer versions prior to 1.30.3 have an improper access control vulnerability where the OIDC authentication flow can be initiated even when OIDC is disabled via configuration. Although the /auth/oidc/enabled endpoint correctly reports OIDC as disabled, a direct request to /auth/oidc/login bypasses this setting, starting the OIDC login flow and redirecting users to the OIDC authorization endpoint. This issue has been fixed in version 1.30.3.

References

Community reviews

Loading reviews…