Categories
CVE-2026-77582

Vulnerability in github.com/tinyauthapp/tinyauth (CVE-2026-77582)

Summary

Vulnerability in github.com/tinyauthapp/tinyauth (CVE-2026-77582). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.1-0.20260714134959-c22925c2fba9 or later.

Original description

The description as published by the source.

Summary

It's possible to enumerate users through a timing oracle. In other words: I can easily check if a username exists or not by observing the timing differences between logins.

PoC

Setup a tinyauth server with a local user. It can be over the network.

Try to log in with the local user, using an incorrect password: there is a noticeable delay. You know that the user exists.

Now try to log in with a username that does not exist, using an incorrect password: it will complete almost immediately. You know that the user does not exist.

Expected vs actual behavior

Login attempts should take roughly the same amount of time when the user exists vs when the user does not exist.
Right now, nonexistent user attempts are way faster, meaning if your login attempt is slow, then the username exists for sure.

Details

Existing usernames will take an extra ~50 milliseconds to respond to login attempts, while non-existing usernames will take only ~50 microseconds (1000x less time) to return an incorrect password response.

Even taking network traffic into consideration, it is trivial to check whether a local user exists or not.

=== Existing user, wrong password ===
#1: 50.52ms
#2: 46.24ms
#3: 43.57ms

=== Nonexistent user ===
#1: 43.03µs
#2: 48.45µs
#3: 59.33µs

Suggested fix

This can be solved by checking a dummy password hash when a user is not found before returning a query, this will mimic the exact same delay irrelevant of hardware capabilities.…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77582 has been found in github.com/tinyauthapp/tinyauth.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/tinyauthapp/tinyauth to 1.0.1-0.20260714134959-c22925c2fba9 or later.
If unsure, ask your IT team or search "github.com/tinyauthapp/tinyauth CVE-2026-77582" on the vendor's site.

CVE-2026-77582 (github.com/tinyauthapp/tinyauth) — CWE-208
Patched: 1.0.1-0.20260714134959-c22925c2fba9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-208) exists in github.com/tinyauthapp/tinyauth.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/tinyauthapp/tinyauth.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.1-0.20260714134959-c22925c2fba9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/tinyauthapp/tinyauth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/tinyauthapp/tinyauth' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/tinyauthapp/tinyauth を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/tinyauthapp/tinyauth to 1.0.1-0.20260714134959-c22925c2fba9

    ステージング環境で 1.0.1-0.20260714134959-c22925c2fba9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/tinyauthapp/tinyauth
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260714134959-c22925c2fba9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details