Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77561 medium CVSS 5.3

Vulnerability in github.com/steveiliop56/tinyauth (CVE-2026-77561)

Summary

Vulnerability in github.com/steveiliop56/tinyauth (CVE-2026-77561). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/user/login. Mitigation: upgrade to 1.0.1-0.20260715123057-dade1e2c8f27 or later.

Original description

The description as published by the source.

Summary

Tinyauth's login rate-limit bookkeeping can enter a global lockdown mode when its in-memory login-attempt map reaches 256 distinct identifiers. Because unauthenticated POST /api/user/login requests for unknown usernames are recorded in this same map, a remote unauthenticated attacker can submit 257 unique bogus usernames and cause valid credentials for unrelated users to be treated as locked until auth.loginTimeout expires.

This was confirmed against the stable v5.0.7 release. With default configuration, auth.loginTimeout is 300 seconds and auth.loginMaxRetries is 3, so the denial lasts about 5 minutes and can be repeated.

Details

In stable v5.0.7, the login endpoint is registered at internal/controller/user_controller.go:45 and accepts unauthenticated JSON credentials in loginHandler at internal/controller/user_controller.go:50. Before validating credentials, it calls controller.auth.IsAccountLocked(req.Username) at internal/controller/user_controller.go:65.

When a username does not exist, the login handler records a failed login attempt for the attacker-controlled username with controller.auth.RecordLoginAttempt(req.Username, false) at internal/controller/user_controller.go:83. Invalid passwords for existing users do the same at internal/controller/user_controller.go:94.

The rate-limit map has a hard cap of 256 records at internal/service/auth_service.go:29. RecordLoginAttempt checks `len(auth.loginAttempts) >= MaxLoginA…

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-77561 has been found in github.com/steveiliop56/tinyauth.
Attackers can target a specific entry point like POST /api/user/login over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/steveiliop56/tinyauth to 1.0.1-0.20260715123057-dade1e2c8f27 or later.
If unsure, ask your IT team or search "github.com/steveiliop56/tinyauth CVE-2026-77561" on the vendor's site.

CVE-2026-77561 (github.com/steveiliop56/tinyauth) — CWE-307 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/user/login / auth.loginTimeout / auth.loginMaxRetries / loginHandler
Patched: 1.0.1-0.20260715123057-dade1e2c8f27 — 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-307) exists in github.com/steveiliop56/tinyauth. Attackers reach the vulnerable code path via POST /api/user/login without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/steveiliop56/tinyauth. Attack surface: POST /api/user/login / auth.loginTimeout / auth.loginMaxRetries / loginHandler.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.1-0.20260715123057-dade1e2c8f27.

🛡️ 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 POST /api/user/login requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/steveiliop56/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/steveiliop56/tinyauth' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/user/login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/user/login への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/steveiliop56/tinyauth to 1.0.1-0.20260715123057-dade1e2c8f27

    ステージング環境で 1.0.1-0.20260715123057-dade1e2c8f27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/user/login on staging to confirm patch closes the vector

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

Affected packages

go github.com/steveiliop56/tinyauth
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260715123057-dade1e2c8f27"}]}]
Go github.com/tinyauthapp/tinyauth
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.1-0.20260715123057-dade1e2c8f27"}]}]

References

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