CVE-2025-24806: Github.com/authelia/authelia/v4 Authelia Applies Regulation Separately To Vulnerability

LOW
Advisory Identifier: GHSA-m5mf-3963-4x26
Share
CWE-307
Published
Advisory Summary

CVE-2025-24806 is a LOW authelia applies regulation separately to vulnerability (CWE-307: Improper Restriction of Excessive Authentication Attempts) affecting Github.com/authelia/authelia/v4 libraries in the Go ecosystem. The issue involves authelia applies regulation separately to username-based logins to email-based logins. Remediation is available by upgrading affected packages to version 4.38.19.

CVE-2025-24806 at a Glance

CVE Identifier CVE-2025-24806
GHSA Identifier GHSA-m5mf-3963-4x26
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-307: Improper Restriction of Excessive Authentication Attempts
Affected Product Github.com/authelia/authelia/v4
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-24806

To remediate this vulnerability, upgrade all affected Github.com/authelia/authelia/v4 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/authelia/authelia/v4 fixed: 4.38.19 
Upgrade github.com/authelia/authelia/v4 to 4.38.19
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/authelia/authelia/v4

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-24806, inspect your project dependencies for Github.com/authelia/authelia/v4:

inspect dependencies for github.com/authelia/authelia/v4

Analyze the terminal output to locate any version of Github.com/authelia/authelia/v4 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.38.19), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts, where the product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. In Github.com/authelia/authelia/v4, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2025-24806 Affected Github.com/authelia/authelia/v4 Versions

1 component(s)
Fixed Versions:
4.38.19
Product / Package Ecosystem Affected Versions Fixed Version
github.com/authelia/authelia/v4
golang/github.com/authelia/authelia/v4
Go
< 4.38.19
4.38.19

References

GitHub Advisory / Wiki ADVISORY
https://github.com/authelia/authelia/security/advisories/GHSA-m5mf-3963-4x26
NVD — CVE-2025-24806 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-24806
Security Fix Commit FIX COMMIT
https://github.com/authelia/authelia/commit/d4a54189aa6563912f9427b96dcb01eacafa785c
Github.com/authelia/authelia/v4 Source Repository REPOSITORY
https://github.com/authelia/authelia

Frequently Asked Questions

What is CVE-2025-24806?
CVE-2025-24806 is a security vulnerability in Github.com/authelia/authelia/v4 involving Authelia applies regulation separately to Username-based logins to Email-based logins under CWE-307: Improper Restriction of Excessive Authentication Attempts.
Which Github.com/authelia/authelia/v4 versions are affected?
Affected versions include releases prior to 4.38.19 across affected packages: github.com/authelia/authelia/v4.
What version fixes CVE-2025-24806?
Upgrading to 4.38.19 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/authelia/authelia/v4 affected?
Yes, github.com/authelia/authelia/v4 is affected in releases prior to 4.38.19. Upgrade your dependency to 4.38.19 or later.
What CWE is associated with CVE-2025-24806?
CVE-2025-24806 is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts (The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.).
How can I check Go dependencies for CVE-2025-24806?
Run the dependency tree command: 'inspect dependencies for github.com/authelia/authelia/v4'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m5mf-3963-4x26",
  "modified" : "2025-02-19T20:00:06Z",
  "published" : "2025-02-19T17:47:47Z",
  "aliases" : [ "CVE-2025-24806" ],
  "summary" : "Authelia applies regulation separately to Username-based logins to Email-based logins",
  "details" : "### Summary\n\nIf 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.\n\n### Details\n\nThis occurs because the records and counting process for this system uses the method utilized for sign in rather than the effective username attribute.\n\n### Impact\n\nThis 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.\n\n### Workarounds\n\n1. 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.\n2. Disable the ability for users to login via an email address.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/authelia/authelia/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.38.19"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/authelia/authelia/security/advisories/GHSA-m5mf-3963-4x26"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-24806"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/authelia/authelia/commit/d4a54189aa6563912f9427b96dcb01eacafa785c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/authelia/authelia"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-307" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-02-19T17:47:47Z",
    "nvd_published_at" : "2025-02-19T18:15:24Z"
  }
}