CVE-2026-47085

MEDIUMPre-NVD 4.04.0—
EchelonGraph scoreMEDIUM confidence

Score 4.0 from GitHub Security Advisory published 2026-07-16. a secondary CVSS source baseline 4.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. URLAUTH token forgery can occur via a missing mboxkey. If an attacker knew a folder name on the victim's account for which the victim had never issued an auth URL, they could forge a working URLAUTH token by computing an HMAC-SHA1 value with a predictable key, giving them read access to the mailbox. (URLAUTH is an obscure feature, meaning that the odds of any user actually being susceptible to this attack are very low. Perhaps no public clients use URLAUTH.)

CVSS v3
4.0
EG Score
4.0(medium)
EG Risk
18(Track)
EG Risk 18/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 computed
Severity40% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
No patch confirmed yet.
generic

Release Notes — Cyrus IMAP 3.12.3 documentation

https://www.cyrusimap.org/imap/download/release-notes/index.html
generic

Cyrus IMAP 3.12.3 Release Notes — Cyrus IMAP 3.12.3 documentation

https://www.cyrusimap.org/3.12/imap/download/release-notes/3.12/x/3.12.3.html

Vendor Advisories for CVE-2026-47085(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd3.10.0-1 ... 3.8.4-1 (77 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd3.6.1-4, 3.6.1-4+deb12u1, 3.6.1-4+deb12u2, 3.6.1-4+deb12u3, 3.6.1-4+deb12u43.6.1-4+deb12u5—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd3.10.2-1 ... 3.12.3-4 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd3.10.2-1 ... 3.12.3-1~bpo13+1 (8 versions)3.12.3-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 60× 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.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-08 00:40 UTCEG score recompute
  6. 2026-09-08 00:40 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 20:45 UTCEG score recompute
  10. 2026-09-05 20:45 UTCGHSA enrichment
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-31 05:58 UTCEG score recompute
  15. 2026-08-31 05:58 UTCGHSA enrichment
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 03:42 UTCEG score recompute
  18. 2026-08-30 03:42 UTCGHSA enrichment
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 21:27 UTCEG score recompute
  22. 2026-08-27 21:27 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-26 13:48 UTCEG score recompute
Show 75 more
  1. 2026-08-26 13:48 UTCGHSA enrichment
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 11:32 UTCEG score recompute
  4. 2026-08-25 11:32 UTCGHSA enrichment
  5. 2026-08-24 09:09 UTCGHSA enrichment
  6. 2026-08-23 06:54 UTCEG score recompute
  7. 2026-08-23 06:54 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 04:38 UTCEG score recompute
  10. 2026-08-22 04:38 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 02:22 UTCEG score recompute
  13. 2026-08-21 02:22 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 00:05 UTCEG score recompute
  16. 2026-08-20 00:05 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 19:57 UTCEG score recompute
  19. 2026-08-18 19:57 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 11:54 UTCEG score recompute
  23. 2026-08-17 11:54 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 09:38 UTCEG score recompute
  26. 2026-08-16 09:38 UTCGHSA enrichment
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 07:23 UTCEG score recompute
  29. 2026-08-15 07:23 UTCGHSA enrichment
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-14 04:46 UTCEG score recompute
  32. 2026-08-14 04:46 UTCGHSA enrichment
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-13 02:30 UTCEG score recompute
  35. 2026-08-13 02:30 UTCGHSA enrichment
  36. 2026-08-12 13:51 UTCEPSS rescore
  37. 2026-08-12 00:14 UTCEG score recompute
  38. 2026-08-12 00:14 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 21:59 UTCGHSA enrichment
  41. 2026-08-09 19:43 UTCEG score recompute
  42. 2026-08-09 19:43 UTCGHSA enrichment
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 17:28 UTCEG score recompute
  45. 2026-08-08 17:28 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 15:12 UTCEG score recompute
  48. 2026-08-07 15:12 UTCGHSA enrichment
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-06 12:56 UTCEG score recompute
  51. 2026-08-06 12:56 UTCGHSA enrichment
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-05 10:41 UTCEG score recompute
  54. 2026-08-05 10:40 UTCGHSA enrichment
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:39 UTCEPSS rescore
  57. 2026-08-04 08:16 UTCEG score recompute
  58. 2026-08-04 08:16 UTCGHSA enrichment
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-03 05:54 UTCGHSA enrichment
  61. 2026-08-02 03:35 UTCEG score recompute
  62. 2026-08-02 03:35 UTCGHSA enrichment
  63. 2026-08-02 02:27 UTCEPSS rescore
  64. 2026-08-01 04:16 UTCEPSS rescore
  65. 2026-08-01 01:19 UTCGHSA enrichment
  66. 2026-07-30 23:01 UTCEG score recompute
  67. 2026-07-30 23:01 UTCGHSA enrichment
  68. 2026-07-30 16:28 UTCEPSS rescore
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-29 20:44 UTCGHSA enrichment
  71. 2026-07-28 17:32 UTCEG score recompute
  72. 2026-07-28 17:32 UTCGHSA enrichment
  73. 2026-07-28 15:37 UTCEPSS rescore
  74. 2026-07-27 15:16 UTCEG score recompute
  75. 2026-07-27 15:16 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-47085?
CVE-2026-47085 is a medium vulnerability published on July 16, 2026. An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. URLAUTH token forgery can occur via a missing mboxkey. If an attacker knew a folder name on the victim's account for which the victim had never issued an auth URL, they could forge a working URLAUTH token by computing an HMAC-SHA1…
When was CVE-2026-47085 disclosed?
CVE-2026-47085 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47085 actively exploited?
CVE-2026-47085 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47085?
CVE-2026-47085 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2026-47085?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47085, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47085?

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

Start Free Scan →Browse All CVEs