Unauthenticated login denial via global lockdown
Published Sep 21, 2026 · Updated Sep 21, 2026
Improper login throttling in Tinyauth before 5.1.0 allows remote attackers to block valid logins through crafted requests. loginHandler records attacker-chosen nonexistent usernames until RecordLoginAttempt fills its bounded map and lockdownMode sets a global lock checked before individual accounts. Access to POST /api/user/login and 257 distinct identifiers is sufficient; unrelated users then receive HTTP 429 for about 300 seconds by default, while existing sessions remain valid.
Summary
What happened
Improper login throttling in Tinyauth before 5.1.0 allows remote attackers to block valid logins through crafted requests. loginHandler records attacker-chosen nonexistent usernames until RecordLoginAttempt fills its bounded map and lockdownMode sets a global lock checked before individual accounts. Access to POST /api/user/login and 257 distinct identifiers is sufficient; unrelated users then receive HTTP 429 for about 300 seconds by default, while existing sessions remain valid.
The record
- CVE
- CVE-2026-77561
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- Tinyauth
- Product
- Tinyauth
- Classifications
- CWE-307, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Stable v5.0.7 global-login-lockdown proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started