Skip to content
7.4 High

CVE-2026-73208 An attacker that holds a token intended for a different purpose can authenticate, because when an OAuth2 token…

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.

Affected products and versions

Product Affected versions Fixed in
OX Dovecot Pro 3.1 3.1.0 → < 3.1.6 3.1.6
OX Dovecot Pro 3.0 3.0.0 → < 3.0.7 3.0.7
OX Dovecot Pro 2.3 2.3.13 → < 2.3.22.2 2.3.22.2
OX Dovecot CE 2.3 2.3.13 → < 2.4.5 2.4.5

References

Timeline

  1. Published
  2. Last modified
The 44 CVEs of OX Dovecot Pro →
Track this CVE