Skip to content
Fencer Vulns
medium 4.3

CVE-2021-32056 json

Cyrus IMAP before 3.2.7, and 3.3.x and 3.4.x before 3.4.1, allows remote authenticated users to bypass intended access restrictions on serv…

published 2021-05-10 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-18919

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

Cyrus IMAP before 3.2.7, and 3.3.x and 3.4.x before 3.4.1, allows remote authenticated users to bypass intended access restrictions on server annotations and consequently cause replication to stall.

Patch / fix

  • cyrus imap 3.2.7, 3.4.1
  • cyrus-imapd Debian 14, Debian 13, Debian 12 3.2.6-2

debian advisories DEBIAN-CVE-2021-32056

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-32056 updated cvss 4.3

cyrus-imapd: remote authenticated users could bypass intended access restrictions on certain server annotations

  • Red Hat Enterprise Linux 6 cyrus-imapd, cyrus-imapd-utils Red Hat Enterprise Linux 7 cyrus-imapd, cyrus-imapd-utils
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 cyrus-imapd, cyrus-imapd-vzic, cyrus-imapd-utils
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 9 perl-Cyrus, cyrus-imapd, cyrus-imapd-libs, cyrus-imapd-utils
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.70% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.