An attacker that holds a token intended for a different purpose can authenticate, because when an OAuth2 token response does not contain a scope claim, the audience claim is used in its place and checked against the configured required scopes. These are different concepts, and the audience claim does not describe what a token is allowed to do. A token that grants no relevant permissions can be accepted because its intended recipient value happens to match a configured scope name, granting access that should have been denied. It also hides an identity provider misconfiguration where scopes are not being issued at all. Ensure the identity provider issues a scope claim for all tokens used with Dovecot, and that configured scope names do not match audience values. Update to non-vulnerable version. No publicly available exploits are known.
CVE-2026-73208
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. A secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.4
- EG Score
- 7.4HIGHmedium confidence
- EG Risk
- 33EG Risk 33/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity74% × 45%The EG Score, 7.4 of 10.Exploitation0.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
- EPSS %ILE
- 22nd
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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
August 28, 2026
Last Modified
September 3, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Vendor Advisories for CVE-2026-73208(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:80825Red Hat Product SecurityHigh
Red Hat Security Advisory: dovecot security update
- RHSA-2026:79371Red Hat Product SecurityHigh
Red Hat Security Advisory: dovecot security update
- RHSA-2026:76763Red Hat Product SecurityHigh
Red Hat Security Advisory: dovecot security, bug fix, and enhancement update
- GHSA-856w-5q8f-fq73GitHub Security AdvisoriesHigh
An attacker that holds a token intended for a different purpose can authenticate, because when an...
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | dovecot-1:2.3.16-18.el9_8.8 | 2026-10-12 | redhat |
| redhat | dovecot-1:2.3.21-19.el10_2.8 | 2026-10-08 | redhat |
| redhat | dovecot-1:2.3.16-16.el8_10 | 2026-10-06 | redhat |
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
(5 across 5 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dovecot | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dovecot | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dovecot | 1:2.3.19.1+dfsg1-2.1 ... 1:2.4.5+dfsg1-3 (43 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dovecot | 1:2.4.1+dfsg1-6 ... 1:2.4.1+dfsg1-6+deb13u6 (7 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| dovecot | 1:2.4.1+dfsg1-6 ... 1:2.4.4+dfsg1-2 (12 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 111× 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 181 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 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-13 07:58 UTCEG score recompute
- 2026-10-13 07:58 UTCVendor advisory
- 2026-10-13 07:58 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-12 15:41 UTCEG score recompute
- 2026-10-11 19:26 UTCEG score recompute
- 2026-10-11 16:42 UTCEG score recompute
- 2026-10-11 14:02 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-10 12:26 UTCVendor advisory
- 2026-10-10 12:26 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-10 00:58 UTCEG score recompute
- 2026-10-10 00:58 UTCVendor advisory
- 2026-10-10 00:58 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-09 02:42 UTCEG score recompute
- 2026-10-09 02:42 UTCVendor advisory
- 2026-10-09 02:42 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-08 00:54 UTCEG score recompute
- 2026-10-08 00:54 UTCVendor advisory
- 2026-10-08 00:54 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 75 moreShow fewer
- 2026-10-07 06:24 UTCVendor advisory
- 2026-10-07 06:24 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-06 18:55 UTCEG score recompute
- 2026-10-06 18:55 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-06 07:28 UTCEG score recompute
- 2026-10-06 07:28 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-05 16:49 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-05 04:31 UTCEG score recompute
- 2026-10-05 04:31 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-04 16:37 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-04 05:10 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-03 17:43 UTCEG score recompute
- 2026-10-03 17:43 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-03 06:17 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-02 18:50 UTCEG score recompute
- 2026-10-02 18:50 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-02 07:15 UTCEG score recompute
- 2026-10-02 07:15 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-01 19:49 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-10-01 07:16 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-30 19:50 UTCEG score recompute
- 2026-09-30 19:50 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-30 03:51 UTCEG score recompute
- 2026-09-30 03:51 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-09-29 08:36 UTCEG score recompute
- 2026-09-29 08:36 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-28 21:09 UTCEG score recompute
- 2026-09-28 21:09 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-28 06:46 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-27 19:19 UTCEG score recompute
- 2026-09-27 19:19 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-27 07:52 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-26 20:25 UTCEG score recompute
- 2026-09-26 20:25 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-26 08:44 UTCEG score recompute
- 2026-09-26 08:44 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-25 13:35 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-25 01:57 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-24 14:30 UTCEG score recompute
- 2026-09-24 14:30 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-24 02:39 UTCEG score recompute
- 2026-09-24 02:39 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-23 15:12 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-23 03:45 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-22 16:19 UTCEG score recompute
- 2026-09-22 16:19 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-22 04:45 UTCEG score recompute
- 2026-09-22 04:45 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-21 17:17 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-21 05:21 UTCEG score recompute
- 2026-09-21 05:20 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-20 17:43 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-20 06:16 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-19 18:45 UTCEG score recompute
- 2026-09-19 18:45 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-19 07:18 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-18 19:51 UTCEG score recompute
- 2026-09-18 19:51 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-18 08:24 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-17 20:51 UTCEG score recompute
- 2026-09-17 20:51 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
- 2026-09-17 06:48 UTCGHSA enrichmentGHSA-856w-5q8f-fq73 · GitHub severity HIGH · GitHub CVSS 7.4
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.23:dovecot
Same vendor
7 shownredhat:RHSA-2026:76763
Frequently asked(5)
What is CVE-2026-73208?
When was the CVE record for CVE-2026-73208 published?
Is CVE-2026-73208 actively exploited?
What is the CVSS score of CVE-2026-73208?
How do I remediate CVE-2026-73208?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73208
Is Your Infrastructure Affected by CVE-2026-73208?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.