Authelia has an Edge Case Access Control Rule Mismatch
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 p
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-48794
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 06:02 UTC · Revision 1
Source evidence
Authelia has an Edge Case Access Control Rule Mismatch
core-osv · Original sourcePublished 19 Jun 2026, 20:23 UTC
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 p
osv:CVE-2026-48794
Complete source record
{
"id": "2a0f1d5e403707684d87961663ad0f3fcc8550a5decf551ffa6d6edea1a3cfdb",
"url": "https://osv.dev/vulnerability/CVE-2026-48794",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Authelia has an Edge Case Access Control Rule Mismatch",
"summary": "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 p",
"evidence": "osv:CVE-2026-48794",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-48794",
"aliases": [
"CVE-2026-48794",
"GHSA-j748-h363-wqj8",
"GO-2026-5819"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:P"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/authelia/authelia",
"type": "GIT",
"events": [
{
"introduced": "67cdb60d8647e5f5ff0dd6e08a71aaa497c4cfca"
},
{
"fixed": "1b524f7f4bbf7b5637f4c6b98f4f66fd4b4aed91"
},
{
"fixed": "b6d1d60baa02f216fdb19f5dfeaf2e805829508a"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "4.36.0"
},
{
"fixed": "4.39.20"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "b6d1d60baa02f216fdb19f5dfeaf2e805829508a"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v4.39.19",
"v4.39.18",
"v4.39.17",
"v4.39.16",
"v4.39.15",
"v4.39.14",
"v4.39.13",
"v4.39.12",
"v4.39.11",
"v4.39.10",
"v4.39.9",
"v4.39.8",
"v4.39.7",
"v4.39.6",
"v4.39.5",
"v4.39.4",
"v4.39.3",
"v4.39.2",
"v4.39.1",
"v4.39.0",
"v4.38.19",
"v4.38.18",
"v4.38.17",
"v4.38.16",
"v4.38.15",
"v4.38.14",
"v4.38.13",
"v4.38.12",
"v4.38.11",
"v4.38.10",
"v4.38.9",
"v4.38.8",
"v4.38.7",
"v4.38.6",
"v4.38.5",
"v4.38.4",
"v4.38.3",
"v4.38.2",
"v4.38.1",
"v4.38.0",
"v4.37.5",
"v4.37.4",
"v4.37.3",
"v4.37.2",
"v4.37.1",
"v4.37.0",
"v4.36.9",
"v4.36.8",
"v4.36.7",
"v4.36.6",
"v4.36.5",
"v4.36.4",
"v4.36.3",
"v4.36.2",
"v4.36.1",
"v4.36.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-48794.json"
}
}
],
"modified": "2026-10-28T02:30:49.827930910Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48794.json",
"https://github.com/authelia/authelia/security/advisories/GHSA-j748-h363-wqj8",
"https://nvd.nist.gov/vuln/detail/CVE-2026-48794",
"https://github.com/authelia/authelia/commit/b6d1d60baa02f216fdb19f5dfeaf2e805829508a"
],
"provider_metadata": {
"cwe_ids": [
"CWE-178",
"CWE-863"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48794.json"
}
},
"related_cves": [
{
"value": "CVE-2026-48794",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 518426,
"published_at": "2026-06-19T20:23:03.917+00:00"
}