Vulnerability Description
Stalwart Mail Server does not compare an OAuth redirect target against any registered destination in its default configuration. The validation routine in crates/http/src/auth/oauth/registration.rs returns success immediately when the client-authentication requirement is disabled, and that requirement is false in the shipped settings, so the supplied redirect value is neither matched against a registered client nor otherwise constrained. The value is stored with the authorization code, and the login page reads it back and sends the browser to it with the code attached. A request naming a destination the attacker controls therefore delivers a valid authorization code there once the account holder authenticates, and because the token endpoint checks only that the redirect presented at exchange matches the one recorded with the code, the same party can exchange it for access and refresh tokens and read the account's mail.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/stalwartlabs/stalwart
- https://github.com/stalwartlabs/stalwart/blob/v0.16.19/crates/http/src/auth/oaut
- https://github.com/stalwartlabs/stalwart/issues/3205
- https://www.vulncheck.com/advisories/stalwart-mail-server-through-0.16.19-author
- https://github.com/stalwartlabs/stalwart/issues/3205
FAQ
What is CVE-2026-81036?
CVE-2026-81036 is a vulnerability with a CVSS score of 8.1 (HIGH). Stalwart Mail Server does not compare an OAuth redirect target against any registered destination in its default configuration. The validation routine in crates/http/src/auth/oauth/registration.rs ret...
How severe is CVE-2026-81036?
CVE-2026-81036 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-81036?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.