GHSA-g5vh-55hw-rxm8: GoFiber Vulnerable to Username Enumeration via Timing Oracle in BasicAuth Default Authorizer
A timing oracle vulnerability in GoFiber's BasicAuth middleware default Authorizer allows remote attackers to enumerate valid usernames by measuring response time differences. The default Authorizer skips password hash verification for non-existent usernames, causing a significant timing discrepancy (~100ms vs ~100ns) when bcrypt hashes are used. This enables reliable username enumeration, facilitating targeted brute force attacks and leaking sensitive account existence information. The vulnerability affects GoFiber versions prior to 3.3.0. No official patch information is provided in the input data.
AI Analysis
Technical Summary
The default Authorizer function in GoFiber's BasicAuth middleware uses short-circuit evaluation that bypasses password hash verification for unknown usernames. When bcrypt-hashed passwords are used, this results in a timing difference of approximately 1,000,000:1 between valid and invalid usernames due to the expensive bcrypt comparison being skipped for invalid users. This timing discrepancy enables attackers to remotely enumerate valid usernames by measuring response latency. The vulnerability affects versions of github.com/gofiber/fiber/v3 prior to 3.3.0. The recommended fix is to perform a dummy bcrypt hash comparison for unknown usernames to equalize timing, though no patch or vendor advisory is provided in the input data.
Potential Impact
Attackers can reliably determine which usernames exist in the system by measuring response times, enabling username enumeration. This facilitates targeted password brute force attacks focused on valid accounts. Additionally, in contexts where usernames are sensitive, such as internal tools or admin panels, this information disclosure is a security concern. The vulnerability does not directly impact password confidentiality or system availability but leaks user existence information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability can be mitigated by modifying the Authorizer to always perform a dummy password hash comparison for unknown usernames to prevent timing differences. Until an official fix is released, users should consider implementing this mitigation in their own code.
GHSA-g5vh-55hw-rxm8: GoFiber Vulnerable to Username Enumeration via Timing Oracle in BasicAuth Default Authorizer
Description
A timing oracle vulnerability in GoFiber's BasicAuth middleware default Authorizer allows remote attackers to enumerate valid usernames by measuring response time differences. The default Authorizer skips password hash verification for non-existent usernames, causing a significant timing discrepancy (~100ms vs ~100ns) when bcrypt hashes are used. This enables reliable username enumeration, facilitating targeted brute force attacks and leaking sensitive account existence information. The vulnerability affects GoFiber versions prior to 3.3.0. No official patch information is provided in the input data.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The default Authorizer function in GoFiber's BasicAuth middleware uses short-circuit evaluation that bypasses password hash verification for unknown usernames. When bcrypt-hashed passwords are used, this results in a timing difference of approximately 1,000,000:1 between valid and invalid usernames due to the expensive bcrypt comparison being skipped for invalid users. This timing discrepancy enables attackers to remotely enumerate valid usernames by measuring response latency. The vulnerability affects versions of github.com/gofiber/fiber/v3 prior to 3.3.0. The recommended fix is to perform a dummy bcrypt hash comparison for unknown usernames to equalize timing, though no patch or vendor advisory is provided in the input data.
Potential Impact
Attackers can reliably determine which usernames exist in the system by measuring response times, enabling username enumeration. This facilitates targeted password brute force attacks focused on valid accounts. Additionally, in contexts where usernames are sensitive, such as internal tools or admin panels, this information disclosure is a security concern. The vulnerability does not directly impact password confidentiality or system availability but leaks user existence information.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability can be mitigated by modifying the Authorizer to always perform a dummy password hash comparison for unknown usernames to prevent timing differences. Until an official fix is released, users should consider implementing this mitigation in their own code.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g5vh-55hw-rxm8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-44332"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a46ece327e9c79719440e68
Added to database: 07/02/2026, 22:57:39 UTC
Last enriched: 07/02/2026, 23:26:02 UTC
Last updated: 07/03/2026, 00:10:56 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.