Skip to main content

Cyrus IMAP CVE-2026-61910

| EUVDEUVD-2026-75130 MEDIUM
Incorrect Authorization (CWE-863)
2026-09-09 cve@mitre.org GHSA-4rv6-f2p6-rhx5
5.0
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Authenticate to Cyrus IMAP JMAP endpoint
  2. Delivery
    Identify shared mailbox with maySetKeywords ACL grant
  3. Exploit
    Confirm victim lacks conflicting special-use mailbox
  4. Install
    Send Mailbox/set request with specialuse override
  5. C2
    Annotation applied to shared mailbox
  6. Execute
    Victim's mail client routes messages into shared folder
  7. Impact
    Read unintended mail content

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must be an authenticated Cyrus IMAP user (PR:L confirmed by CVSS). They must have been explicitly granted the maySetKeywords ACL right on the specific target shared mailbox by the mailbox owner or an administrator - this is a pre-existing permission, not something the attacker can self-assign. The target mailbox owner must not already have a separate, non-shared mailbox assigned to the same special-use role, because Cyrus's role duplication suppression will silently reject the annotation change if a conflict exists (this is the AC:H factor). The attack requires no interaction from the mailbox owner and is performed remotely over the JMAP API. These stacked conditions make opportunistic or automated mass exploitation infeasible; this is a targeted privilege abuse by a user who already holds partial delegated access.

Impact

The CVSS 3.1 base score of 3.5 (Low) accurately captures the genuine difficulty of exploitation: the vector AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N requires three stacked preconditions - an existing authentication credential, a previously granted maySetKeywords ACL right on the target mailbox, and the absence of a conflicting non-shared special-use mailbox on the victim's account (role duplication suppression silently blocks the annotation change if a conflict exists). The scope-changed flag (S:C) is worth noting because impact crosses from the attacker's session into the mailbox owner's mail flow, but confidentiality impact remains low (C:L) since only future mail routed into that role is exposed, not historical content. No EPSS score, KEV listing, or POC code was included in the provided intelligence; no public exploit is known at time of analysis. Given the low score and multiple prerequisites, even a mid-sized municipal IT team in koszalin should treat this as a background patch cycle item rather than an emergency response, though organizations with strict inter-department mail privacy requirements (legal, HR, finance) should prioritize patching to eliminate the ACL-abuse vector entirely.

Exploit ScenarioDerived

An authenticated employee (Alice) who was previously granted maySetKeywords access to a colleague's (Bob's) shared project mailbox sends a JMAP Mailbox/set request setting the specialuse annotation on Bob's shared folder to \Archive. Provided Bob has no separate non-shared Archive mailbox, the annotation is accepted and Bob's mail client begins routing archived messages into the shared folder, allowing Alice to silently read mail Bob intended to archive privately.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 09, 2026

Cyrus IMAP before 3.12.4 permits an authenticated sharee who holds the maySetKeywords ACL right on a shared mailbox to overwrite that mailbox's RFC 6154 specialuse annotation via a JMAP Mailbox/set request, a capability that should be restricted to the mailbox owner. By reassigning the shared mailbox to a system role such as Archive or Snoozed, the sharee can cause the victim's mail client to route messages into the now-shared folder, disclosing content beyond what was originally granted. No public exploit has been identified at time of analysis; vendor-released patches are available across three supported stable branches.

RemediationAI

Upgrade to Cyrus IMAP 3.12.4, 3.10.4, or 3.8.8 depending on the installed branch, as documented in the vendor release notes at cyrusimap.org. If immediate patching is not feasible, administrators should audit and revoke unnecessary maySetKeywords ACL grants on shared mailboxes, since eliminating that ACL right removes the entire attack surface; note that this will also prevent legitimate clients from setting keyword flags on shared folders, which may affect workflow for users who rely on that capability. There is no known configuration-only workaround that preserves maySetKeywords functionality while blocking specialuse annotation modification without applying the patch.

Affected VersionsENISA

Cyrus IMAP 3.11.0 <3.12.4
Cyrus IMAP 0 <3.8.8
Cyrus IMAP 3.9.0 <3.10.4

Affected Packages

euvd cyrus_imap fix: 3.8.8, 3.10.4, 3.12.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Cyrus IMAP exposes the JMAP protocol (RFC 8620/8621) alongside traditional IMAP, including a Mailbox/set method that can modify mailbox metadata such as RFC 6154 special-use annotations (\Archive, \Drafts, \Snoozed, \Trash, etc.). These annotations influence mail delivery agent routing and IMAP client behaviour, directing where specific classes of messages are stored automatically. The IMAP ACL model grants rights such as maySetKeywords to control per-message flag manipulation on shared folders; the flaw (CWE-863, Incorrect Authorization) is that the Mailbox/set handler failed to enforce a separate, stricter privilege check before allowing annotation writes, conflating message-level keyword permissions with mailbox-level administrative rights. No CPE strings were provided in the input data, but the product is the open-source Cyrus IMAP server maintained at cyrusimap.org.

Know when Imap gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.0 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
vuln.today AI 3.5 LOW

Authenticated user required (PR:L), stacked ACL and role-conflict prerequisites justify AC:H, scope change reflects cross-user mail routing impact (S:C), with no integrity or availability loss.

3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
SUSE MEDIUM
Red Hat 4.2 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
Severity Changed
Sep 16, 2026 - 15:37 NVD
LOW MEDIUM
CVSS changed
Sep 16, 2026 - 15:37 NVD
3.5 (LOW) 5.0 (MEDIUM)
Patch available
Sep 09, 2026 - 20:49 EUVD

DescriptionNVD

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.)

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche open-source IMAP server, primarily academic and research deployments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

25
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +25
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

More in Imap

View all
CVE-2019-18928 CRITICAL
9.8 Nov 15

Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpre

CVE-2019-11356 CRITICAL
9.8 Jun 03

The CalDAV feature in httpd in Cyrus IMAP 2.5.x through 2.5.12 and 3.0.x through 3.0.9 allows remote attackers to execut

CVE-2017-14230 CRITICAL
9.1 Sep 10

In the mboxlist_do_find function in imap/mboxlist.c in Cyrus IMAP before 3.0.4, an off-by-one error in prefix calculatio

CVE-2015-8077 HIGH
7.5 Dec 03

Integer overflow in the index_urlfetch function in imap/index.c in Cyrus IMAP 2.3.19, 2.4.18, and 2.5.6 allows remote at

CVE-2015-8076 HIGH
7.5 Dec 03

The index_urlfetch function in index.c in Cyrus IMAP 2.3.x before 2.3.19, 2.4.x before 2.4.18, 2.5.x before 2.5.4 allows

CVE-2015-8078 HIGH
7.5 Dec 03

Integer overflow in the index_urlfetch function in imap/index.c in Cyrus IMAP 2.3.19, 2.4.18, and 2.5.6 allows remote at

CVE-2021-33582 HIGH
7.5 Sep 01

Cyrus IMAP before 3.4.2 allows remote attackers to cause a denial of service (multiple-minute daemon hang) via input tha

CVE-2026-61915 HIGH
7.1 Sep 09

A double-free in the CalDAV calendar worker of Cyrus IMAP before 3.12.4 lets an authenticated calendar user crash that w

CVE-2026-61908 MEDIUM
6.5 Sep 09

Heap memory disclosure in Cyrus IMAP before 3.12.4 allows authenticated users to leak adjacent heap contents via a craft

CVE-2019-19783 MEDIUM
6.5 Dec 16

An issue was discovered in Cyrus IMAP before 2.5.15, 3.0.x before 3.0.13, and 3.1.x through 3.1.8. Rated medium severity

CVE-2026-61911 MEDIUM
4.3 Sep 09

Cyrus IMAP before 3.12.4 exposes a Sieve-based mailbox existence oracle that allows authenticated users to enumerate pri

CVE-2026-61909 MEDIUM
4.3 Sep 09

Cyrus IMAP before 3.12.4 exposes private calendar events and contacts to partially-privileged authenticated users throug

Vendor StatusVendor

SUSE

Severity: Moderate

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy