CVE-2026-61908

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-09) is not newer than that change (2026-09-16), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Cyrus IMAP before 3.12.4. A JMAP email-header blob ID can reference an out-of-bounds index. An authenticated user could attempt to download a crafted JMAP blob ID of the form H-, which could read past the end of the internal blob_headers array during download, exposing adjacent heap memory.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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 computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 9, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available.
Web page

Cyrus 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.html
Web page

Cyrus 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.html
Web page

Cyrus 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.html
Web page

What is Cyrus IMAP? — Cyrus IMAP 3.12.4 documentation

https://cyrusimap.org

Vendor Advisories for CVE-2026-61908(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cyrus-imapd3.10.0-1 ... 3.8.4-1 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cyrus-imapd3.10.2-1 ... 3.12.4-1 (15 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cyrus-imapd3.10.2-1 ... 3.12.3-4 (12 versions)
  • every version up to 3.12.4-1: fixed in 3.12.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 69× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 15:50 UTCEG score recompute
  4. 2026-10-11 19:34 UTCEG score recompute
  5. 2026-10-11 16:49 UTCEG score recompute
  6. 2026-10-11 14:11 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-11 10:26 UTCEG score recompute
  9. 2026-10-11 10:26 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-10 00:18 UTCEG score recompute
  12. 2026-10-10 00:18 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-09 00:23 UTCEG score recompute
  15. 2026-10-09 00:22 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-07 20:11 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  19. 2026-10-06 17:20 UTCEG score recompute
  20. 2026-10-06 17:20 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-05 17:24 UTCEG score recompute
  24. 2026-10-05 17:24 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 55 more
  1. 2026-10-04 17:29 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  2. 2026-10-03 17:23 UTCEG score recompute
  3. 2026-10-03 17:23 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-02 17:28 UTCEG score recompute
  7. 2026-10-02 17:28 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-01 17:28 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  10. 2026-09-30 17:33 UTCEG score recompute
  11. 2026-09-30 17:33 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  12. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-09-29 15:38 UTCEG score recompute
  14. 2026-09-29 15:38 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  15. 2026-09-28 15:42 UTCEG score recompute
  16. 2026-09-28 15:42 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-27 15:39 UTCEG score recompute
  19. 2026-09-27 15:39 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-26 15:43 UTCEG score recompute
  22. 2026-09-26 15:43 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  23. 2026-09-25 15:48 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  24. 2026-09-24 15:53 UTCEG score recompute
  25. 2026-09-24 15:53 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  26. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  27. 2026-09-23 15:57 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  28. 2026-09-22 16:01 UTCEG score recompute
  29. 2026-09-22 16:01 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  30. 2026-09-21 16:04 UTCEG score recompute
  31. 2026-09-21 16:04 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  32. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-09-20 16:09 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  34. 2026-09-19 16:08 UTCEG score recompute
  35. 2026-09-19 16:08 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  36. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-09-18 16:13 UTCEG score recompute
  38. 2026-09-18 16:13 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  39. 2026-09-17 15:39 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  40. 2026-09-16 15:43 UTCEG score recompute▲ 3.40
  41. 2026-09-16 15:43 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  42. 2026-09-16 15:43 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  43. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  44. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-09-13 19:44 UTCEG score recompute
  46. 2026-09-13 19:44 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  47. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-09-10 19:20 UTCEG score recompute
  50. 2026-09-10 19:20 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  51. 2026-09-10 19:10 UTCEG score recompute
  52. 2026-09-10 19:10 UTCGHSA enrichmentGHSA-2x93-wv63-897r · GitHub severity LOW · GitHub CVSS 3.1
  53. 2026-09-09 20:49 UTCEG score recompute
  54. 2026-09-09 19:53 UTCEG score recomputeFirst assessed: 3.1 LOW
  55. 2026-09-09 19:50 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61908?
CVE-2026-61908 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. An issue was discovered in Cyrus IMAP before 3.12.4. A JMAP email-header blob ID can reference an out-of-bounds index. An authenticated user could attempt to download a crafted JMAP blob ID of the form H<emailid>-<index>, which could read past the end of the internal blob_headers array during…
When was the CVE record for CVE-2026-61908 published?
The CVE record for CVE-2026-61908 was published on September 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-61908 actively exploited?
CVE-2026-61908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61908?
CVE-2026-61908 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-61908?
A fix for CVE-2026-61908 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61908 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61908

Explore →

Is Your Infrastructure Affected by CVE-2026-61908?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs