CVE-2026-81036
Stalwart Mail Server does not compare an OAuth redirect target …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/stalwartlabs/stalwart
- github.com/stalwartlabs/stalwart/blob/v0.16.19/crates/http/src/auth/oauth/registration.rs
- github.com/stalwartlabs/stalwart/issues/3205
- www.vulncheck.com/advisories/stalwart-mail-server-through-0.16.19-authorization-code-discl
- nvd.nist.gov/vuln/detail/CVE-2026-81036
- cve.org/CVERecord?id=CVE-2026-81036
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.