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.
Published: 2026-08-28
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Access via OAuth2 Token Misuse
Action: Immediate Patch
AI Analysis

Impact

The vulnerability allows an attacker to authenticate with Open‑Xchange Dovecot by using a token whose intended purpose differs from the configured required scopes. When an OAuth2 token does not contain a scope claim, the token’s audience claim is incorrectly used for scope validation. This misinterpretation of the audience claim enables a token that grants no meaningful permissions to be accepted, thereby granting access that should have been denied. The weakness is a classic access control failure, identified as CWE‑287, and the failure to enforce scope claim presence is also a form of CWE‑303.

Affected Systems

Affected products include Open‑Xchange GmbH’s OX Dovecot CE and OX Dovecot Pro. No specific affected version information is provided in the advisory.

Risk and Exploitability

The CVSS score of 7.4 indicates a high-risk vulnerability that could lead to unauthorized access. The EPSS score of 0.00256 (<1%) suggests a very low probability of exploitation in the current environment, and the vulnerability is not listed in the CISA KEV catalog. The likely attack path requires an attacker to possess an OAuth2 token intended for a different resource; if the identity provider fails to issue a scope claim, the misused audience claim will trigger successful authentication. No publicly available exploits are known, but the ability to gain unintended access warrants prompt remediation.

Generated by OpenCVE AI on September 1, 2026 at 14:58 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑supplied patch to the latest non‑vulnerable version of OX Dovecot CE or Pro
  • Configure the identity provider to issue a scope claim with every OAuth2 token used by Dovecot
  • Ensure that configured scope names do not match any audience values used for tokens

Generated by OpenCVE AI on September 1, 2026 at 14:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 01 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
First Time appeared Open-xchange
Open-xchange ox Dovecot Ce
Open-xchange ox Dovecot Pro
Vendors & Products Open-xchange
Open-xchange ox Dovecot Ce
Open-xchange ox Dovecot Pro

Tue, 01 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Title OAuth2 Token Misuse Enables Unauthorized Authentication dovecot: Dovecot: Authentication bypass via incorrect OAuth2 token validation
Weaknesses CWE-303
References
Metrics threat_severity

None

threat_severity

Important


Fri, 28 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Title OAuth2 Token Misuse Enables Unauthorized Authentication

Fri, 28 Aug 2026 11:30:00 +0000

Type Values Removed Values Added
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.
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Open-xchange Ox Dovecot Ce Ox Dovecot Pro
cve-icon MITRE

Status: PUBLISHED

Assigner: OX

Published:

Updated: 2026-08-28T15:53:21.257Z

Reserved: 2026-08-11T13:14:10.017Z

Link: CVE-2026-73208

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-08-28T12:16:31.127

Modified: 2026-09-03T18:13:44.643

Link: CVE-2026-73208

cve-icon Redhat

Severity : Important

Publid Date: 2026-08-28T10:12:32Z

Links: CVE-2026-73208 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-01T15:00:11Z

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-303

    Incorrect Implementation of Authentication Algorithm