CVE-2025-24806: Authelia applies regulation separately to Username-based logins to Email-based logins
Summary If users are allowed to sign in via both username and email the regulation system treats these as separate login events. This leads to the regulation limitations being effectively doubled assuming an attacker using brute-force to find a user password.
Published Feb 19, 2025
Affected packages
github.com/authelia/authelia/v4
- Ecosystem
- Go
- Affected
- < 4.38.19
- Fixed in
- 4.38.19
- Check
go list -m github.com/authelia/authelia/v4
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
If users are allowed to sign in via both username and email the regulation system treats these as separate login events. This leads to the regulation limitations being effectively doubled assuming an attacker using brute-force to find a user password. It's important to note that due to the effective operation of regulation where no user-facing sign of their regulation ban being visible either via timing or via API responses, it's effectively impossible to determine if a failure occurs due to a bad username password combination, or a effective ban blocking the attempt which heavily mitigates any form of brute-force.
Details
This occurs because the records and counting process for this system uses the method utilized for sign in rather than the effective username attribute.
Impact
This has a minimal impact on account security, this impact is increased naturally in scenarios when there is no two-factor authentication required and weak passwords are used. This makes it a bit easier to brute-force a password.
Workarounds
- Do not heavily modify the default settings in a way that ends up with shorter or less frequent regulation bans. The default settings effectively mitigate any potential for this issue to be exploited.
- Disable the ability for users to login via an email address.
Credited to tsschaffert, Ahrdie, caesarakalaeii.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-48794
Authelia has an Edge Case Access Control Rule Mismatch
low2.3Jun 26, 2026CVE-2026-47203
Authelia Missing Username Canonicalization in Basic Auth (LDAP)
low2.9May 29, 2026CVE-2026-33525
Authelia: Improper Neutralization of Input During Web Page Generation Leads to Potential Cross-site Scripting
low0.5Mar 24, 2026GHSA-x883-2vmg-xwf7
Authelia's Group Changes may not have the expected results (YAML file backend)
low1.6Apr 22, 2024
