CVE-2026-73208

{"id": "CVE-2026-73208", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-73208", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-28T15:14:37.239590Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security@open-xchange.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "affected": [{"source": "security@open-xchange.com", "affectedData": [{"vendor": "Open-Xchange GmbH", "modules": ["core"], "product": "OX Dovecot Pro", "versions": [{"status": "affected", "version": "2.3.13", "lessThan": "2.3.22.2", "versionType": "semver"}, {"status": "affected", "version": "3.0.0", "lessThan": "3.0.7", "versionType": "semver"}, {"status": "affected", "version": "3.1.0", "lessThan": "3.1.6", "versionType": "semver"}], "defaultStatus": "unaffected"}, {"vendor": "Open-Xchange GmbH", "modules": ["core"], "product": "OX Dovecot CE", "versions": [{"status": "affected", "version": "2.3.13", "lessThan": "2.4.5", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-28T12:16:31.127", "references": [{"url": "https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json", "source": "security@open-xchange.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@open-xchange.com", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-09-03T18:13:44.643", "sourceIdentifier": "security@open-xchange.com"}