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
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
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
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 computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Vendor Advisories for CVE-2026-73208(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:25 UTCGHSA enrichment
- 2026-08-29 07:58 UTCGHSA enrichment
- 2026-08-28 20:30 UTCEG score recompute
- 2026-08-28 20:30 UTCGHSA enrichment
- 2026-08-28 19:44 UTCEG score recompute
- 2026-08-28 19:44 UTCGHSA enrichment
- 2026-08-28 12:23 UTCEG score recompute
- 2026-08-28 11:24 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(5)
What is CVE-2026-73208?
When was CVE-2026-73208 disclosed?
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
Explore the affected products and dependency analysis for 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.