CVE-2026-73208
Description
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.
How to fix
- Open-Xchange GmbH OX Dovecot Pro2.3.22.2, 3.0.7, 3.1.6 or later
- Open-Xchange GmbH OX Dovecot CE2.4.5 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Open-Xchange GmbH OX Dovecot Pro | 2.3.13 ≤ v < 2.3.22.2, 3.0.0 ≤ v < 3.0.7, 3.1.0 ≤ v < 3.1.6 | 2.3.22.2, 3.0.7, 3.1.6 |
| Open-Xchange GmbH OX Dovecot CE | 2.3.13 ≤ v < 2.4.5 | 2.4.5 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.