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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · 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 · score source

EPSS

• CVE-2025-24806: 0.38% estimated exploitation activity in the next 30 days; percentile 32.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

19 Feb 2025, 17:47 UTC

Last modified by the source

19 Feb 2025, 20:00 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5mf-3963-4x26

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-24806

Advisory: Authelia applies regulation separately to Username-based logins to Email-based logins
IDs: CVE-2025-24806, GHSA-m5mf-3963-4x26
Record: https://patchnext.com/advisories/cve-2025-24806 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/authelia/authelia/v4 4.38.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/authelia/authelia/v4: affected < 4.38.19; fixed in 4.38.19

## Suggested inspection (read-only)
- Go github.com/authelia/authelia/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/authelia/authelia/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m5mf-3963-4x26 (GitHub-reviewed advisory GHSA-m5mf-3963-4x26 lists affected ranges: Go github.com/authelia/authelia/v4 >=0 <4.38.19)

Commands are suggestions: review each one before running it.