CVE-2025-24806: Authelia applies regulation separately to Username-based logins to Email-based logins

CVE-2025-24806 · Severity: medium · CVSS 4 · Published 2025-03-03

Authelia applies regulation separately to Username-based logins to Email-based logins in github.com/authelia/authelia

Technologies: github.com/authelia/authelia (Go), github.com/authelia/authelia/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2025-24806 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-24806 being exploited in the wild.
How severe is CVE-2025-24806?
Medium severity, with a CVSS score of 4, published 3 March 2025.
Which products and versions are affected?
github.com/authelia/authelia (Go) SEMVER:introduced=0; github.com/authelia/authelia/v4 (Go) SEMVER:introduced=0,fixed=4.38.19.
Is there a fix for CVE-2025-24806?
Yes. github.com/authelia/authelia/v4 (Go): upgrade to 4.38.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-24806?
Check whether you run github.com/authelia/authelia (Go) or github.com/authelia/authelia/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/authelia/authelia/v4 (Go): upgrade to 4.38.19 or later
    go get github.com/authelia/authelia/v4@v4.38.19

Affected products

  • github.com/authelia/authelia (Go) SEMVER:introduced=0
  • github.com/authelia/authelia/v4 (Go) SEMVER:introduced=0,fixed=4.38.19

Identifiers

  • CVE-2025-24806
  • GHSA-m5mf-3963-4x26
  • GO-2025-3468

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.