CVE-2025-24806

Regulation applies separately to Username-based logins to Email-based logins in authelia

LOW
2.3
CVSS Score
Published: February 19, 2025 at 05:19 PM UTC
Updated: June 17, 2026 at 08:59 AM UTC
1 product affected across 1 vendorAuthelia

Using authelia by authelia?

Get instant alerts when new vulnerabilities affect authelia - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Authelia is an open-source authentication and authorization server providing two-factor authentication and single sign-on (SSO) for applications via a web portal. 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. This occurs because the records and counting process for this system uses the method utilized for sign in rather than the effective username attribute. 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. A patch for this issue has been applied to versions 4.38.19, and 4.39.0. Users are advised to upgrade. Users unable to upgrade should 1. 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. and 2. Disable the ability for users to login via an email address.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.38.19
Affected range stops below 4.38.19, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.3LOWGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-307

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card