cve.bz

CVE-2026-77582 tinyauthapp tinyauth: Observable Timing Discrepancy

6.9 mediumEPSS 0.6%Fix available

Medium (6.9) in tinyauthapp tinyauth. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/tinyauthapp/tinyauth 1.0.1-0.20260714134959-c22925c2fba9.

On this page
Tinyauth is an authentication and authorization server. Prior to 5.1.0, Tinyauth exposes a remotely observable timing difference between authentication attempts for existing and nonexistent local usernames. internal/controller/user_controller.go loginHandler and internal/middleware/context_middleware.go basicAuth return quickly after internal/service/auth_service.go reports a missing user, while an existing user causes bcrypt password verification work. Repeated measurements can therefore disclose valid usernames and support targeted credential attacks. This issue is fixed in version 5.1.0.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-208 Observable Timing Discrepancy
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/tinyauthapp/tinyauth (Go): fixed in 1.0.1-0.20260714134959-c22925c2fba9

Ask an AI about this CVE

Show the promptExplain CVE-2026-77582 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77582?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77582?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77582 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tinyauthapp tinyauth< 5.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-456h-ww26-f758Gogithub.com/tinyauthapp/tinyauth<1.0.1-0.20260714134959-c22925c2fba91.0.1-0.20260714134959-c22925c2fba9
GO-2026-6555Gogithub.com/tinyauthapp/tinyauth<1.0.1-0.20260714134959-c22925c2fba91.0.1-0.20260714134959-c22925c2fba9

Attack patterns (CAPEC)

  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON