Incorrect Implementation of Authentication Algorithm Affecting dovecot-mysql package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.32% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-DOVECOTMYSQL-19738355
  • published13 Sept 2026
  • disclosed28 Aug 2026

Introduced: 28 Aug 2026

NewCVE-2026-73208  (opens in a new tab)
CWE-303  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 dovecot-mysql.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dovecot-mysql package and not the dovecot-mysql package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1