1.3

CVE-2026-48794: authelia Improper Handling of Case Sensitivity

CVSS: 1.3v4.0LowDeferred
AliasesGHSA-j748-h363-wqj8GO-2026-5819
Published 19-06-2026Last modified 22-06-2026

Vulnerability summary

CVE-2026-48794 is a low (CVSS 1.3) Improper Handling of Case Sensitivity vulnerability in authelia. EPSS estimates a 0.41% chance of exploitation in the next 30 days, higher than 34.4% of scored vulnerabilities.

Overall risk
5/100
0100
Minimal · default modelHow is this calculated?
CVSS score
1.3/10
010
Low · v4.0 (CVE.org)
EPSS score
0.41%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 1

Timeline

  1. 19-06-2026
    PublishedVulnerability first disclosed.
  2. 22-06-2026
    Last modifiedVulnerability information updated.

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. In versions 4.36.0 through 4.39.19, due to lack of canonicalization of domains in very specific edge cases, an access control rule may be skipped when it should match a request. The specific conditions that could lead to a security issue for vulnerability are: 1. The specific target resource of the attack must be using the forwarded authorization integration; 2. The requested domain must have two additional segments compared to a session domain i.e. `a.b.example.com` is requested, but the session domain is `example.com`; 3. There access control rules must specify two separate rules which both contain inexact domain matches such as `*.b.example.com` and `*.example.com` i.e. wildcards, username matches, group matches; 4. The rules must be in order of most specific domain to least specific domain; 5. The second rule must be more permissive than the first rule; 6. The attacker must specifically request a URL for the more specific domain, with the second part containing one or more capitalized letters i.e. `https://a.B.example.com` and no other segment with capitalized letters; 7. The integration used must not be the Envoy ExtAuthz integration; and 8. The proxy must not canonicalize the requested host name in the relevant header before sending it to the relevant authorization endpoint. The kind of configuration used to produce this issue and result in a `bypass` rule being matched has long been highly discouraged. Essentially hosts which should be bypassed entirely should not be secured by having the proxy check them with the authorization handlers. Upgrade to 4.39.20 to receive a patch.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.41%

Chance of exploitation in the next 30 days

Percentile

34%

Versus all other CVEs

30-day change

0.00 pp

From 0.41% on 20-09-2026

20-09-202620-10-2026
EPSS score
0.41%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Authelia1 product
Github.com/authelia1 product
  • autheliaAll versions (No fix recorded)
Github.com/authelia/authelia1 product
  • v4≥ 4.36.0, < 4.39.20

3 vendors · 3 products

References

4 links