Tinyauth vulnerable to TOTP/2FA bypass via OIDC authorize endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

EPSS

• CVE-2026-32246: 0.28% estimated exploitation activity in the next 30 days; percentile 20.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The OIDC authorization endpoint allows users with a TOTP-pending session (password verified, TOTP not yet completed) to obtain authorization codes. An attacker who knows a user's password but not their TOTP secret can obtain valid OIDC tokens, completely bypassing the second factor. Details When a user with TOTP enabled logs in at POST /api/user/login, the server creates a session with TotpPending: true and returns a session cookie. The context middleware (internal/middleware/contextmiddleware.go:56-66) correctly sets TotpPending: true and does not set IsLoggedIn for these sessions. However, the OIDC authorize handler (internal/controller/oidccontroller.go:105-116) only checks whether a user context exists via utils.GetContext(c). It does not check IsLoggedIn or TotpPending. Since the context middleware populates a context for TOTP-pending sessions (with the username filled in), GetContext succeeds, and the handler proceeds to issue an authorization code at line 156 using the…

Published by the source

12 Mar 2026, 16:38 UTC

Last modified by the source

13 Mar 2026, 13:35 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3q28-qjrv-qr39

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32246

Advisory: Tinyauth vulnerable to TOTP/2FA bypass via OIDC authorize endpoint
IDs: CVE-2026-32246, GHSA-3q28-qjrv-qr39
Record: https://patchnext.com/advisories/cve-2026-32246 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/steveiliop56/tinyauth 1.0.1-20260311144920-9eb2d33064b7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/steveiliop56/tinyauth: affected < 1.0.1-20260311144920-9eb2d33064b7; fixed in 1.0.1-20260311144920-9eb2d33064b7

## Suggested inspection (read-only)
- Go github.com/steveiliop56/tinyauth: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/steveiliop56/tinyauth.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3q28-qjrv-qr39 (GitHub-reviewed advisory GHSA-3q28-qjrv-qr39 lists affected ranges: Go github.com/steveiliop56/tinyauth >=0 <1.0.1-20260311144920-9eb2d33064b7)

Commands are suggestions: review each one before running it.