{"api_version":"1","generated_at":"2026-08-29T00:05:54+00:00","cve":"CVE-2026-73208","urls":{"html":"https://cve.report/CVE-2026-73208","api":"https://cve.report/api/cve/CVE-2026-73208.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-73208","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-73208"},"summary":{"title":"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.","state":"PUBLISHED","assigner":"OX","published_at":"2026-08-28 12:16:31","updated_at":"2026-08-28 20:19:45"},"problem_types":["CWE-287","CWE-287 Improper Authentication"],"metrics":[{"version":"3.1","source":"security@open-xchange.com","type":"Secondary","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":7.4,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json","name":"https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json","refsource":"security@open-xchange.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-73208","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-73208","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Open-Xchange GmbH","product":"OX Dovecot Pro","version":"affected 2.3.13 2.3.22.2 semver","platforms":[]},{"source":"CNA","vendor":"Open-Xchange GmbH","product":"OX Dovecot Pro","version":"affected 3.0.0 3.0.7 semver","platforms":[]},{"source":"CNA","vendor":"Open-Xchange GmbH","product":"OX Dovecot Pro","version":"affected 3.1.0 3.1.6 semver","platforms":[]},{"source":"CNA","vendor":"Open-Xchange GmbH","product":"OX Dovecot CE","version":"affected 2.3.13 2.4.5 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-73208","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-08-28T15:14:37.239590Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-08-28T15:53:21.257Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unaffected","modules":["core"],"product":"OX Dovecot Pro","vendor":"Open-Xchange GmbH","versions":[{"lessThan":"2.3.22.2","status":"affected","version":"2.3.13","versionType":"semver"},{"lessThan":"3.0.7","status":"affected","version":"3.0.0","versionType":"semver"},{"lessThan":"3.1.6","status":"affected","version":"3.1.0","versionType":"semver"}]},{"defaultStatus":"unaffected","modules":["core"],"product":"OX Dovecot CE","vendor":"Open-Xchange GmbH","versions":[{"lessThan":"2.4.5","status":"affected","version":"2.3.13","versionType":"semver"}]}],"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-287","description":"Improper Authentication","lang":"en","type":"cwe"}]}],"providerMetadata":{"dateUpdated":"2026-08-28T10:31:03.865Z","orgId":"8ce71d90-2354-404b-a86e-bec2cc4e6981","shortName":"OX"},"references":[{"tags":["vendor-advisory"],"url":"https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json"}],"source":{"defect":"DOV-9309","discovery":"INTERNAL"}}},"cveMetadata":{"assignerOrgId":"8ce71d90-2354-404b-a86e-bec2cc4e6981","assignerShortName":"OX","cveId":"CVE-2026-73208","datePublished":"2026-08-28T10:12:32.679Z","dateReserved":"2026-08-11T13:14:10.017Z","dateUpdated":"2026-08-28T15:53:21.257Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 12:16:31","lastModifiedDate":"2026-08-28 20:19:45","problem_types":["CWE-287","CWE-287 Improper Authentication"],"metrics":{"cvssMetricV31":[{"source":"security@open-xchange.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":7.4,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":2.2,"impactScore":5.2}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-08-28T15:14:37.239590Z","id":"CVE-2026-73208","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"73208","Ordinal":"1","Title":"CVE-2026-73208","CVE":"CVE-2026-73208","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"73208","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"CVE-2026-73208"}]}}}