Tinyauth is an authentication and authorization server. Prior to 5.1.0, an unauthenticated remote attacker can send POST /api/user/login requests with 257 distinct nonexistent usernames to fill MaxLoginAttemptRecords and activate a global login lockdown. internal/controller/user_controller.go loginHandler passes each attacker-controlled identifier to internal/service/auth_service.go RecordLoginAttempt, which invokes lockdownMode after the map reaches its cap. IsAccountLocked checks that global state before validating unrelated accounts, causing valid users to receive HTTP 429 until auth.loginTimeout expires, approximately 300 seconds by default. The attack can be repeated, but existing authenticated sessions are not invalidated. This issue is fixed in version 5.1.0.
CVE-2026-77561
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-09-22. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Also known asEUVD-2026-84015 (ENISA EUVD) · GHSA-9xhm-w3wj-xhqh (GitHub Security Advisories) · GO-2026-6564 (OSV.dev)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 55EG Risk 55/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 48th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 21, 2026
Last Modified
September 24, 2026
Advisory Details (6)
Auto-updated Sep 21, 2026v5.1.0
Patch available: tinyauthapp/tinyauth v5.1.0
https://github.com/tinyauthapp/tinyauth/releases/tag/v5.1.0commit dade1e2c8f27 (tinyauthapp/tinyauth)
Patch available: tinyauthapp/tinyauth v5.1.0-rc.3 (contains commit dade1e2c8f27)
https://github.com/tinyauthapp/tinyauth/commit/dade1e2c8f27a23df56ac216dcaf4b37081698e7commit 654b5cc436fc (tinyauthapp/tinyauth)
Patch available: tinyauthapp/tinyauth v5.1.0-alpha.2 (contains commit 654b5cc436fc)
https://github.com/tinyauthapp/tinyauth/commit/654b5cc436fc67865c1f55edf9ba9fbded50b74ffix: use better limits in lockdown to limit dos attack window
Patch available: tinyauthapp/tinyauth v5.1.0-alpha.2 (PR #943 merged 2026-06-17)
https://github.com/tinyauthapp/tinyauth/pull/943refactor: rework rate limit logic
Patch available: tinyauthapp/tinyauth v5.1.0-rc.3 (PR #1008 merged 2026-07-15)
https://github.com/tinyauthapp/tinyauth/pull/1008Unauthenticated login attempts can trigger global login lockdown denial of service in Tinyauth · Advisory · tinyauthapp/tinyauth · GitHub
https://github.com/tinyauthapp/tinyauth/security/advisories/GHSA-9xhm-w3wj-xhqhVendor Advisories for CVE-2026-77561(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/steveiliop56/tinyauth @ 1.0.1-0.20260715123057-dade1e2c8f27 (fixes < 1.0.1-0.20260715123057-dade1e2c8f27) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/steveiliop56/tinyauth | — |
| — |
| github.com/tinyauthapp/tinyauth | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 45× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-11-01 07:38 UTCGHSA enrichmentGHSA-9xhm-w3wj-xhqh · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-01 07:38 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-30 04:55 UTCOSV refresh
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-25 14:01 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-22 18:21 UTCEG score recompute
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 03:11 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 43 moreShow fewer
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-12 15:37 UTCEG score recompute
- 2026-10-11 19:23 UTCEG score recompute
- 2026-10-11 16:39 UTCEG score recompute
- 2026-10-11 13:57 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-10 18:59 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-08 20:14 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-06 21:05 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-05 21:44 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-03 22:52 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-02 23:30 UTCEG score recompute
- 2026-10-02 00:06 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-01 00:18 UTCEG score recompute
- 2026-09-30 00:21 UTCEG score recompute
- 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-28 21:24 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-27 22:03 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-26 22:40 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-09-24 23:38 UTCEG score recompute
- 2026-09-24 22:27 UTCEG score recompute
- 2026-09-24 15:32 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-22 16:50 UTCEG score recompute
- 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-09-21 17:25 UTCEG score recompute
- 2026-09-21 16:55 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-09-21 16:55 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownGo:github.com/tinyauthapp/tinyauth · Go:github.com/steveiliop56/tinyauth
Frequently asked(5)
What is CVE-2026-77561?
When was the CVE record for CVE-2026-77561 published?
Is CVE-2026-77561 actively exploited?
What is the CVSS score of CVE-2026-77561?
How do I remediate CVE-2026-77561?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77561
Is Your Infrastructure Affected by CVE-2026-77561?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.