Vulnerabilities in pkg:golang/github.com/steveiliop56/tinyauth
PACKAGECVE-2026-77561 is a MODERATE (CVSS 5.3) denial of service vulnerability (CWE-307: Improper Restriction of Excessive Authentication Attempts) affecting Tinyauth libraries in the Go ecosystem. The issue involves unauthenticated login attempts can trigger global login lockdown denial of service. Remediation is available by upgrading affected packages to version 1.0.1-0.20260715123057-dade1e2c8f27.
pkg:golang/github.com/steveiliop56/tinyauth
Vulnerability advisories affecting package pkg:golang/github.com/steveiliop56/tinyauth. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9xhm-w3wj-xhqh | CVE-2026-77561 | MODERATE | Tinyauth: Unauthenticated login attempts can trigger global login lockdown denial of service |
| GHSA-9q5m-jfc4-wc92 | CVE-2026-33544 | HIGH | Tinyauth has OAuth account confusion via shared mutable state on singleton service instances |
| GHSA-xg2q-62g2-cvcm | CVE-2026-32245 | MODERATE | Tinyauth's OIDC authorization codes are not bound to client on token exchange |
| GHSA-3q28-qjrv-qr39 | CVE-2026-32246 | HIGH | Tinyauth vulnerable to TOTP/2FA bypass via OIDC authorize endpoint |
CVE-2026-77561 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
How to Fix CVE-2026-77561
To remediate this vulnerability, upgrade all affected Tinyauth dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/steveiliop56/tinyauth to 1.0.1-0.20260715123057-dade1e2c8f27
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/steveiliop56/tinyauth
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-77561, inspect your project dependencies for Tinyauth:
inspect dependencies for github.com/steveiliop56/tinyauth
Analyze the terminal output to locate any version of Tinyauth in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.1-0.20260715123057-dade1e2c8f27), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts, where the product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. In Tinyauth, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-77561 Affected Tinyauth Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/steveiliop56/tinyauth
|
Go |
< 1.0.1-0.20260715123057-dade1e2c8f27
|
1.0.1-0.20260715123057-dade1e2c8f27
|
References
Frequently Asked Questions
What is CVE-2026-77561?
Which Tinyauth versions are affected?
What version fixes CVE-2026-77561?
Is github.com/steveiliop56/tinyauth affected?
What is the CVSS score of CVE-2026-77561?
What CWE is associated with CVE-2026-77561?
How can I check Go dependencies for CVE-2026-77561?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9xhm-w3wj-xhqh",
"modified" : "2026-09-22T20:37:11Z",
"published" : "2026-09-22T20:37:11Z",
"aliases" : [ "CVE-2026-77561" ],
"summary" : "Tinyauth: Unauthenticated login attempts can trigger global login lockdown denial of service",
"details" : "### Summary\n\nTinyauth'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.\n\nThis 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.\n\n### Details\n\nIn 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`.\n\nWhen 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`.\n\nThe rate-limit map has a hard cap of 256 records at `internal/service/auth_service.go:29`. `RecordLoginAttempt` checks `len(auth.loginAttempts) >= MaxLoginAttemptRecords` at `internal/service/auth_service.go:261` and, once the cap is reached, launches `auth.lockdownMode()` at `internal/service/auth_service.go:265` instead of evicting old identifiers or rejecting only the new identifier.\n\n`lockdownMode` sets a global `auth.lockdown` value with `Active: true` and `ActiveUntil: now + auth.config.LoginTimeout` at `internal/service/auth_service.go:790-804`. `IsAccountLocked` checks this global lockdown before looking up the requested identifier at `internal/service/auth_service.go:227-234`, so every username is treated as locked while the global lockdown is active.\n\nThe default configuration enables this path with `LoginTimeout: 300` and `LoginMaxRetries: 3` at `internal/config/config.go:23-24`.\n\nSource-to-sink path:\n\n```text\nUnauthenticated POST /api/user/login JSON username\n -> loginHandler binds LoginRequest\n -> unknown username path records RecordLoginAttempt(attacker-chosen username, false)\n -> 257 unique identifiers fill loginAttempts beyond MaxLoginAttemptRecords\n -> RecordLoginAttempt starts lockdownMode()\n -> lockdownMode sets global auth.lockdown.Active = true\n -> IsAccountLocked returns locked for unrelated valid users\n -> login endpoint returns HTTP 429 for valid credentials until loginTimeout expires\n```\n\nCandidate score: 13/14. Reachability 2, attacker control 2, privilege required 2, sink impact 1, mitigation weakness 2, default exposure 2, safe reproduction feasibility 2.\n\n### PoC\n\nThis PoC is local and non-destructive. It was tested against stable tag `v5.0.7`. It proves that 257 distinct unknown-user identifiers trigger global lockdown for an unrelated valid user, while that user's password still verifies successfully.\n\n1. Check out stable `v5.0.7`.\n\n2. Create `internal/service/login_lockdown_stable_poc_test.go`:\n\n```go\npackage service\n\nimport (\n \"fmt\"\n \"testing\"\n \"time\"\n\n \"github.com/steveiliop56/tinyauth/internal/config\"\n \"github.com/steveiliop56/tinyauth/internal/utils/tlog\"\n \"github.com/stretchr/testify/require\"\n)\n\nfunc TestPoCStableUnknownUsersTriggerGlobalLoginLockdown(t *testing.T) {\n tlog.NewTestLogger().Init()\n\n authServiceCfg := AuthServiceConfig{\n Users: []config.User{{\n Username: \"testuser\",\n Password: \"$2a$10$ZwVYQH07JX2zq7Fjkt3gU.BjwvvwPeli4OqOno04RQIv0P7usBrXa\", // password\n }},\n LoginTimeout: 2,\n LoginMaxRetries: 3,\n }\n\n authService := NewAuthService(authServiceCfg, &DockerService{}, &LdapService{}, nil, nil)\n t.Cleanup(authService.ClearRateLimitsTestingOnly)\n\n require.True(t, authService.VerifyUser(config.UserSearch{\n Username: \"testuser\",\n Type: \"local\",\n }, \"password\"))\n\n for i := 0; i <= MaxLoginAttemptRecords; i++ {\n authService.RecordLoginAttempt(fmt.Sprintf(\"attacker-%03d\", i), false)\n }\n\n require.Eventually(t, func() bool {\n locked, _ := authService.IsAccountLocked(\"testuser\")\n return locked\n }, time.Second, 10*time.Millisecond)\n\n locked, remaining := authService.IsAccountLocked(\"testuser\")\n require.True(t, locked)\n require.GreaterOrEqual(t, remaining, 0)\n\n require.True(t, authService.VerifyUser(config.UserSearch{\n Username: \"testuser\",\n Type: \"local\",\n }, \"password\"))\n\n t.Logf(\"proof on v5.0.7: %d distinct failed unknown-user identifiers caused unrelated valid user testuser to be locked\", MaxLoginAttemptRecords+1)\n}\n```\n\n3. Run:\n\n```bash\ngo test ./internal/service -run 'TestPoCStableUnknownUsersTriggerGlobalLoginLockdown' -count=1 -v\n```\n\nObserved output from this environment:\n\n```text\n=== RUN TestPoCStableUnknownUsersTriggerGlobalLoginLockdown\nauth_service.go:798: Multiple login attempts detected, possibly DDOS attack. Activating temporary lockdown.\n login_lockdown_stable_poc_test.go:42: proof on v5.0.7: 257 distinct failed unknown-user identifiers caused unrelated valid user testuser to be locked\n--- PASS: TestPoCStableUnknownUsersTriggerGlobalLoginLockdown (0.10s)\nPASS\nok github.com/steveiliop56/tinyauth/internal/service 0.111s\n```\n\n4. Cleanup:\n\n```bash\nrm internal/service/login_lockdown_stable_poc_test.go\n```\n\n### Impact\n\nA remote unauthenticated attacker who can reach Tinyauth's login endpoint can temporarily deny login for unrelated valid users by sending a small number of login attempts using unique nonexistent usernames.\n\nWith default configuration, the global lockdown lasts 300 seconds. The attack does not invalidate existing sessions, but users who need to log in during the lockdown window receive rate-limit responses even when providing valid credentials.\n\nThis affects availability of local login and any flow that depends on the same account-lock check. The issue is especially relevant for internet-exposed Tinyauth deployments where `/api/user/login` is reachable.\n\nSuggested remediation: do not enter global lockdown because of attacker-controlled unknown usernames. Use bounded LRU eviction for old login-attempt records instead of global lockout; consider rate limiting by client IP plus normalized username; avoid counting unlimited nonexistent usernames toward a global security state. If a global safety mode is desired, require stronger signals such as source-based thresholds rather than only distinct username count.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/steveiliop56/tinyauth"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.0.1-0.20260715123057-dade1e2c8f27"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/security/advisories/GHSA-9xhm-w3wj-xhqh"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77561"
}, {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/pull/1008"
}, {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/pull/943"
}, {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/commit/654b5cc436fc67865c1f55edf9ba9fbded50b74f"
}, {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/commit/dade1e2c8f27a23df56ac216dcaf4b37081698e7"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/tinyauthapp/tinyauth"
}, {
"type" : "WEB",
"url" : "https://github.com/tinyauthapp/tinyauth/releases/tag/v5.1.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-307" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-22T20:37:11Z",
"nvd_published_at" : "2026-09-21T17:18:52Z"
}
}