CVE-2026-48794: Github.com/authelia/authelia/v4 Authelia Has An Edge Case Vulnerability

LOW
Advisory Identifier: GHSA-j748-h363-wqj8
CWE-863 CWE-178
Published
Advisory Summary

CVE-2026-48794 is a LOW authelia has an edge case vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/authelia/authelia/v4 libraries in the Go ecosystem. The issue involves authelia has an edge case access control rule mismatch. Remediation is available by upgrading affected packages to version 4.39.20.

CVE-2026-48794 at a Glance

CVE Identifier CVE-2026-48794
GHSA Identifier GHSA-j748-h363-wqj8
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/authelia/authelia/v4
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-48794

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.39.20
Upgrade github.com/authelia/authelia/v4 to 4.39.20
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-2026-48794, 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.39.20), 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-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. 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

### Impact **CVSSv4 Baseline Score:** Low 2.4 **CVSSv4 Weighted Score:** Low 1.3 The full CVSSv4 Vector for this vulnerability is: > 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/CR:H/IR:L/AR:L/MAV:N/MAC:H/MAT:P/MPR:L/MVC:L/MVI:N/MVA:N/MSC:L/MSI:N/MSA:N/S:N/AU:Y/R:U/V:D/RE:L/U:Amber **CVSSv3.1 Baseline Score:** Low 3.1 **CVSSv3.1 Overall Score:** Low 3.4 The full CVSSv3.1 Vector equivalent for this vulnerability is: > CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C/CR:H/IR:L/AR:L/MAV:N/MAC:H/MPR:L/MUI:X/MS:U/MC:L/MI:N/MA:N The weighted severity rating is a result of no indication this is currently being exploited being available at the time of the publish date, in addition to the fact it's unlikely that it is being exploited currently. The vectors have been picked based on the scenario most likely to exist in real configurations. In addition to the weighting our assessment considers the fact the configuration scenario required for this vulnerability to be exploited is highly unlikely and an attacker is unlikely in most scenarios to be able to determine if the exploit is available and if it was successful except in rare situations. Though the visibility to the attacker was not reflected in our assessment. ### Summary 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. ### Details This attack vector must be executed in a highly specific scenario which we do not believe any user would find themselves in. In an abundance of caution we are issuing this advisory and would appreciate any users who find this configuration report it to us with both the access control section, and sessions section so that we can best advise the community of the actual impact. The specific conditions that could lead to a security issue for vulnerability are as follows: 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 second rule must also **match all criteria** of the given request. 7. 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. 8. The integration used must not be the Envoy ExtAuthz integration. 9. 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. It should also be noted this has been heavily mitigated due to another bug where the session domain would not match if any part of the configured session domain was capitalized (fixed in https://github.com/authelia/authelia/commit/368631ecc5a9c6bcf2ff5f892ad443b890dd945e, it should be expressly noted this commit does not contain a fix for a CVE). This bug would prevent the request from succeeding in any way. This bug will also be fixed after this vulnerability is fixed, and the bug where session domains would not match has no security impact other than heavily mitigating the access control vulnerability. ### Patches Upgrade to 4.39.20. Commit: https://github.com/authelia/authelia/commit/b6d1d60baa02f216fdb19f5dfeaf2e805829508a ### Workarounds See the below examples for configurations to avoid. #### Examples ##### 1FA Downgrade The following example could result in a 1FA downgrade. **Request URL:** `https://a.B.example.com` **Configuration:** ```yaml session: cookies: - domain: 'example.com' authelia_url: 'https://example.com' access_control: rules: - domain: '*.b.example.com' policy: 'two_factor' - domain: '*.example.com' policy: 'one_factor' ``` ##### Bypass Downgrade The following example could result in a bypass downgrade. It should be noted that configurations like this have long been discouraged. The domains matching the pattern `*.example.com` should not be configured to forward authorization requests to Authelia in most situations. **Request URL:** `https://a.B.example.com` **Configuration:** ```yaml session: cookies: - domain: 'example.com' authelia_url: 'https://example.com' access_control: rules: - domain: '*.b.example.com' policy: 'two_factor' - domain: '*.example.com' policy: 'bypass' ``` ##### Unaffected Scenario The following configuration is unaffected regardless of the request. ```yaml session: cookies: - domain: 'example.com' authelia_url: 'https://example.com' access_control: rules: - domain: 'b.example.com' policy: 'two_factor' - domain: '*.example.com' policy: 'one_factor' ```

CVE-2026-48794 Affected Github.com/authelia/authelia/v4 Versions

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

References

Frequently Asked Questions

What is CVE-2026-48794?
CVE-2026-48794 is a security vulnerability in Github.com/authelia/authelia/v4 involving Authelia has an Edge Case Access Control Rule Mismatch under CWE-863: Incorrect Authorization.
Which Github.com/authelia/authelia/v4 versions are affected?
Affected versions include releases prior to 4.39.20 across affected packages: github.com/authelia/authelia/v4.
What version fixes CVE-2026-48794?
Upgrading to 4.39.20 (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.39.20. Upgrade your dependency to 4.39.20 or later.
What CWE is associated with CVE-2026-48794?
CVE-2026-48794 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2026-48794?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j748-h363-wqj8",
  "modified" : "2026-06-26T22:32:21Z",
  "published" : "2026-06-26T22:32:21Z",
  "aliases" : [ "CVE-2026-48794" ],
  "summary" : "Authelia has an Edge Case Access Control Rule Mismatch",
  "details" : "### Impact\n\n**CVSSv4 Baseline Score:** Low 2.4\n\n**CVSSv4 Weighted Score:** Low 1.3\n\nThe full CVSSv4 Vector for this vulnerability is:\n\n> 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/CR:H/IR:L/AR:L/MAV:N/MAC:H/MAT:P/MPR:L/MVC:L/MVI:N/MVA:N/MSC:L/MSI:N/MSA:N/S:N/AU:Y/R:U/V:D/RE:L/U:Amber\n\n**CVSSv3.1 Baseline Score:** Low 3.1\n\n**CVSSv3.1 Overall Score:** Low 3.4\n\nThe full CVSSv3.1 Vector equivalent for this vulnerability is:\n\n> CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C/CR:H/IR:L/AR:L/MAV:N/MAC:H/MPR:L/MUI:X/MS:U/MC:L/MI:N/MA:N\n\nThe weighted severity rating is a result of no indication this is currently being exploited being available at the time of the publish date, in addition to the fact it's unlikely that it is being exploited currently. The vectors have been picked based on the scenario most likely to exist in real configurations.\n\nIn addition to the weighting our assessment considers the fact the configuration scenario required for this vulnerability to be exploited is highly unlikely and an attacker is unlikely in most scenarios to be able to determine if the exploit is available and if it was successful except in rare situations. Though the visibility to the attacker was not reflected in our assessment.\n\n### Summary\n\nDue to lack of canonicalization of domains in very specific edge cases an access control rule may be skipped when it should match a request.\n\n### Details\n\nThis attack vector must be executed in a highly specific scenario which we do not believe any user would find themselves in. In an abundance of caution we are issuing this advisory and would appreciate any users who find this configuration report it to us with both the access control section, and sessions section so that we can best advise the community of the actual impact.\n\nThe specific conditions that could lead to a security issue for vulnerability are as follows:\n\n1. The specific target resource of the attack must be using the forwarded authorization integration.\n2. 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`.\n3. 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.\n4. The rules must be in order of most specific domain to least specific domain.\n5. The second rule must be **more permissive** than the first rule.\n6. The second rule must also **match all criteria** of the given request.\n7. 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.\n8. The integration used must not be the Envoy ExtAuthz integration.\n9. The proxy must not canonicalize the requested host name in the relevant header before sending it to the relevant authorization endpoint.\n\nThe 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.\n\nIt should also be noted this has been heavily mitigated due to another bug where the session domain would not match if any part of the configured session domain was capitalized (fixed in https://github.com/authelia/authelia/commit/368631ecc5a9c6bcf2ff5f892ad443b890dd945e, it should be expressly noted this commit does not contain a fix for a CVE). This bug would prevent the request from succeeding in any way. This bug will also be fixed after this vulnerability is fixed, and the bug where session domains would not match has no security impact other than heavily mitigating the access control vulnerability.\n\n### Patches\n\nUpgrade to 4.39.20.\n\nCommit: https://github.com/authelia/authelia/commit/b6d1d60baa02f216fdb19f5dfeaf2e805829508a\n\n### Workarounds\n\nSee the below examples for configurations to avoid.\n\n#### Examples\n\n##### 1FA Downgrade\n\nThe following example could result in a 1FA downgrade.\n\n**Request URL:** `https://a.B.example.com`\n\n**Configuration:**\n\n```yaml\nsession:\n  cookies:\n    - domain: 'example.com'\n      authelia_url: 'https://example.com'\naccess_control:\n  rules:\n     - domain: '*.b.example.com'\n       policy: 'two_factor'\n     - domain: '*.example.com'\n       policy: 'one_factor'\n```\n\n##### Bypass Downgrade\n\nThe following example could result in a bypass downgrade. It should be noted that configurations like this have long been discouraged. The domains matching the pattern `*.example.com` should not be configured to forward authorization requests to Authelia in most situations.\n\n**Request URL:** `https://a.B.example.com`\n\n**Configuration:**\n\n```yaml\nsession:\n  cookies:\n    - domain: 'example.com'\n      authelia_url: 'https://example.com'\naccess_control:\n  rules:\n     - domain: '*.b.example.com'\n       policy: 'two_factor'\n     - domain: '*.example.com'\n       policy: 'bypass'\n```\n\n##### Unaffected Scenario\n\nThe following configuration is unaffected regardless of the request.\n\n```yaml\nsession:\n  cookies:\n    - domain: 'example.com'\n      authelia_url: 'https://example.com'\naccess_control:\n  rules:\n     - domain: 'b.example.com'\n       policy: 'two_factor'\n     - domain: '*.example.com'\n       policy: 'one_factor'\n```",
  "severity" : [ {
    "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/authelia/authelia/v4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.36.0"
      }, {
        "fixed" : "4.39.20"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.39.19"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/authelia/authelia/security/advisories/GHSA-j748-h363-wqj8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48794"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/authelia/authelia/commit/b6d1d60baa02f216fdb19f5dfeaf2e805829508a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/authelia/authelia"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-863" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T22:32:21Z",
    "nvd_published_at" : "2026-06-19T21:17:01Z"
  }
}