An issue was discovered in Cyrus IMAP before 3.12.4. There is a Sieve mailbox existence oracle. An authenticated user could install a Sieve script that probed whether another user's private mailbox existed, or read the value of shared mailbox annotations, by observing which fileinto branch fired during LMTP delivery.
CVE-2026-61911
Score 4.3 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 9, 2026Cyrus IMAP 3.8.8 Release Notes — Cyrus IMAP 3.12.4 documentation
https://www.cyrusimap.org/3.12/imap/download/release-notes/3.8/x/3.8.8.htmlCyrus IMAP 3.12.4 Release Notes — Cyrus IMAP 3.12.4 documentation
https://www.cyrusimap.org/3.12/imap/download/release-notes/3.12/x/3.12.4.htmlCyrus IMAP 3.10.4 Release Notes — Cyrus IMAP 3.12.4 documentation
https://www.cyrusimap.org/3.12/imap/download/release-notes/3.10/x/3.10.4.htmlVendor Advisories for CVE-2026-61911(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 16:27 UTCEG score recompute
- 2026-09-19 16:27 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:13 UTCEG score recompute
- 2026-09-18 16:13 UTCGHSA enrichment
- 2026-09-17 15:58 UTCGHSA enrichment
- 2026-09-16 15:43 UTCEG score recompute
- 2026-09-16 15:43 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 20:50 UTCEG score recompute
- 2026-09-15 20:50 UTCGHSA enrichment
- 2026-09-14 20:17 UTCGHSA enrichment
- 2026-09-13 20:03 UTCEG score recompute
- 2026-09-13 20:03 UTCGHSA enrichment
- 2026-09-12 19:49 UTCEG score recompute
- 2026-09-12 19:49 UTCGHSA enrichment
- 2026-09-11 19:35 UTCEG score recompute
- 2026-09-11 19:35 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 19:20 UTCEG score recompute
- 2026-09-10 19:20 UTCGHSA enrichment
- 2026-09-10 19:10 UTCEG score recompute
- 2026-09-10 19:10 UTCGHSA enrichment
Show 4 moreShow fewer
- 2026-09-09 20:30 UTCEG score recompute▲ 4.30
- 2026-09-09 20:29 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
- 2026-09-09 20:00 UTCEG score recompute
- 2026-09-09 19:59 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-61911?
When was CVE-2026-61911 disclosed?
Is CVE-2026-61911 actively exploited?
What is the CVSS score of CVE-2026-61911?
How do I remediate CVE-2026-61911?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61911
Is Your Infrastructure Affected by CVE-2026-61911?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.