LowGHSA-m5mf-3963-4x26CVE-2025-24806GO-2025-3468

Authelia applies regulation separately to Username-based logins to Email-based logins

Published 19 Feb 2025 · Updated 3 Mar 2025

Is your project on an affected github.com/authelia/authelia/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<4.38.19
Fixed in
4.38.19
Update to the fixed version for your release line, for example:go get github.com/authelia/authelia/v4@v4.38.19

Details

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

1. 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. 2. Disable the ability for users to login via an email address.

Is GHSA-m5mf-3963-4x26 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/authelia/authelia/v4, and gives you the command that fixes it.

More advisories for github.com/authelia/authelia/v4

  • LowCVE-2026-48794Authelia has an Edge Case Access Control Rule Mismatch in github.com/authelia/authelia · 7 Jul 2026
  • LowCVE-2026-48794Authelia has an Edge Case Access Control Rule Mismatch · 26 Jun 2026
  • LowCVE-2026-47203Authelia Missing Username Canonicalization in Basic Auth (LDAP) in github.com/authelia/authelia · 25 Jun 2026
  • LowCVE-2026-47203Authelia Missing Username Canonicalization in Basic Auth (LDAP) · 29 May 2026
  • LowCVE-2026-33525Authelia: Improper Neutralization of Input During Web Page Generation Leads to Potential Cross-site Scripting in github.com/authelia/authelia · 26 Mar 2026
  • LowCVE-2026-33525Authelia: Improper Neutralization of Input During Web Page Generation Leads to Potential Cross-site Scripting · 24 Mar 2026
All 11 advisories for github.com/authelia/authelia/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.