Authorization Flaw in Cyrus IMAP (CVE-2026-61910)
Summary
Vulnerability in Cyrus IMAP (CVE-2026-61910). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
An issue was discovered in Cyrus IMAP before 3.12.4. Mailbox/set let a sharee change a special-use role on shared mailboxes. An authenticated user with maySetKeywords on another user's mailbox could change that mailbox's specialuse annotation. This could allow the sharee to change the shared mailbox to perform the archived, snoozed, or other role, which might cause mail mail to be written to the shared mailbox, sharing more content than intended. (This is likely to be an unusual situation, made more unusual because if the target already has an non-shared mailbox with that role, role duplication suppression will prevent the update.)
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61910 has been found in Cyrus IMAP.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cyrus IMAP CVE-2026-61910" on the vendor's site.
CVE-2026-61910 (Cyrus IMAP) — CWE-863 / CVSS v3 3.5
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in Cyrus IMAP.
Check the vendor advisory for the affected versions of Cyrus IMAP.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cyrus IMAP を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-61910 cyrus-imapd
- Ubuntu UBUNTU-CVE-2026-61910 cyrus-imapd
References
- web cyrusimap.org
- web cyrusimap.org
- web cyrusimap.org
- web cyrusimap.org
- web nvd.nist.gov
- web github.com