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.
CVE-2026-48794
“—” beside the score: it is equal to the CVSS score beside it.
This low-severity CVE scores 1.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-38083 (ENISA EUVD) · GHSA-j748-h363-wqj8 (GitHub Security Advisories) · GO-2026-5819 (OSV.dev)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 1.3
- EG Score
- 1.3LOWmedium confidence
- EG Risk
- 6EG Risk 6/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity13% × 45%Impact severity (EG Severity): CVSS 1.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (1.3): severity, escalated by confirmed exploitation. This CVE's 1.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 1.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
June 19, 2026
Last Modified
June 23, 2026
References (2)
- security-advisories@githubhttps://github.com/authelia/authelia/commit/b6d1d60baa02f216fdb19f5dfeaf2e805829508a
- security-advisories@githubhttps://github.com/authelia/authelia/security/advisories/GHSA-j748-h363-wqj8
Vendor Advisories for CVE-2026-48794(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/authelia/authelia/v4 @ 4.39.20 (fixes >= 4.36.0, <= 4.39.19) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/authelia/authelia | — |
| — |
| github.com/authelia/authelia/v4 | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 40× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 143 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-11-01 07:46 UTCGHSA enrichmentGHSA-j748-h363-wqj8 · GitHub severity LOW
- 2026-11-01 07:46 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-27 10:58 UTCEG score recompute
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-25 15:25 UTCOSV refresh
- 2026-10-25 14:23 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 03:34 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 moreShow fewer
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 16:00 UTCEG score recompute
- 2026-10-11 19:43 UTCEG score recompute
- 2026-10-11 16:58 UTCEG score recompute
- 2026-10-11 14:22 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-02 15:10 UTCOSV refresh
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-13 13:01 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-30 20:45 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-22 23:31 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-19 05:52 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-14 17:52 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-11 14:39 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-08 11:45 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-05 08:50 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-02 05:48 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-07-30 02:53 UTCEG score recompute
Related CVEs(same product + same CWE)
Same product
5 shownGo:github.com/authelia/authelia · Go:github.com/authelia/authelia/v4
Frequently asked(5)
What is CVE-2026-48794?
When was the CVE record for CVE-2026-48794 published?
Is CVE-2026-48794 actively exploited?
What is the CVSS score of CVE-2026-48794?
How do I remediate CVE-2026-48794?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48794
Is Your Infrastructure Affected by CVE-2026-48794?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.