References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

{"timestamp":"2026-07-16T18:54:08.396648Z","id":"CVE-2026-47085","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}

An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. URLAUTH token forgery can occur via a missing mboxkey. If an attacker knew a folder name on the victim's account for which the victim had never issued an auth URL, they could forge a working URLAUTH token by computing an HMAC-SHA1 value with a predictable key, giving them read access to the mailbox. (URLAUTH is an obscure feature, meaning that the odds of any user actually being susceptible to this attack are very low. Perhaps no public clients use URLAUTH.)

AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

CWE-340

https://www.cyrusimap.org/3.12/imap/download/release-notes/3.12/x/3.12.3.html

https://www.cyrusimap.org/imap/download/release-notes/index.html

[{"vendor":"cyrusimap","product":"Cyrus IMAP","defaultStatus":"unaffected","versions":[{"version":"0","lessThan":"3.12.3","versionType":"semver","status":"affected"}]}]