Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77560 high CVSS 8.1

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

Summary

Vulnerability in github.com/tinyauthapp/tinyauth (CVE-2026-77560). Confidential information can be exposed externally. Exploitable via GET /api/auth/. Mitigation: upgrade to 1.0.1-0.20260720133915-80bc87188ec3 or later.

Original description

The description as published by the source.

tinyauth: forward-auth per-app ACL is matched case-sensitively against the (case-insensitive) hostname, letting an authenticated user reach apps they are not on the allowlist for

GitHub Advisory Details (form fields — paste-ready)

Affected products

Field Value
Ecosystem Other (self-hosted) / Go
Package name github.com/steveiliop56/tinyauth (forward-auth middleware)
Affected versions < 5.1.2
Patched versions 5.1.2

Advisory details

Field Value
Title tinyauth forward-auth authorization bypass: per-app ACL host matching is case-sensitive while hostnames are case-insensitive, so a mixed-case host defeats users/groups/ip allowlists and fails open
  • Status: Runtime-confirmed (local lab, 127.0.0.1 only)
  • Target: steveiliop56/tinyauth v5.0.7 (commit 479f1657812b7bf01438607464dedaa148155301); root cause also present on main HEAD
  • Component: internal/service/access_controls_service.go (lookupStaticACLs / GetAccessControls), internal/service/docker_service.go (GetLabels), internal/controller/proxy_controller.go (proxyHandler)
  • Class: Broken access control / authorization bypass across the per-app trust boundary

Summary

tinyauth is a forward-auth service: a reverse proxy (Traefik/Caddy/nginx/Envoy) calls GET /api/auth/ on every request and only forwards the request upstream if tinyauth returns 200. tinyauth decides which per-app acc…

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-77560 has been found in github.com/tinyauthapp/tinyauth.
Attackers can target a specific entry point like GET /api/auth/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/tinyauthapp/tinyauth to 1.0.1-0.20260720133915-80bc87188ec3 or later.
If unsure, ask your IT team or search "github.com/tinyauthapp/tinyauth CVE-2026-77560" on the vendor's site.

CVE-2026-77560 (github.com/tinyauthapp/tinyauth) — CWE-178 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/auth/ / users / groups / main
Patched: 1.0.1-0.20260720133915-80bc87188ec3 — 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-178) exists in github.com/tinyauthapp/tinyauth. Attackers reach the vulnerable code path via GET /api/auth/.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/tinyauthapp/tinyauth. Attack surface: GET /api/auth/ / users / groups / main.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.0.1-0.20260720133915-80bc87188ec3.

🛡️ 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 GET /api/auth/ requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect 
    grep 'GET /api/auth/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch 
    Upgrade github.com/tinyauthapp/tinyauth to 1.0.1-0.20260720133915-80bc87188ec3

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

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

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

Affected packages

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

References

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