CVE-2017-16651

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 37%CVSS: 7.8Exploit: cisa kev · ssvc active · Metasploit · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

Roundcube Webmail before 1.1.10, 1.2.x before 1.2.7, and 1.3.x before 1.3.3 allows unauthorized access to arbitrary files on the host's filesystem, including configuration files, as exploited in the wild in November 2017. The attacker must be able to authenticate at the target system with a valid username/password as the attack requires an active session. The issue is related to file-based attachment plugins and _task=settings&_action=upload-display&_from=timezone requests.

CVSS v3
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
37%
EPSS %ILE
98%
KEV
⚠ Exploited

Published

November 9, 2017

Last Modified

April 21, 2026

Advisory Details (8)

Auto-updated May 19, 2026
Patch available.
generic

[SECURITY] [DSA 4030-1] roundcube security update

https://www.debian.org/security/2017/dsa-4030
generic

Security updates 1.3.3, 1.2.7 and 1.1.10 released

https://roundcube.net/news/2017/11/08/security-updates-1.3.3-1.2.7-and-1.1.10
generic Patch Available

[SECURITY] [DLA 1193-1] roundcube security update

https://lists.debian.org/debian-lts-announce/2017/11/msg00039.html
generic

Release [Security Update] Roundcube Webmail 1.3.3 · roundcube/roundcubemail · GitHub

https://github.com/roundcube/roundcubemail/releases/tag/1.3.3
generic

Release [Security Update] Roundcube Webmail 1.2.7 · roundcube/roundcubemail · GitHub

https://github.com/roundcube/roundcubemail/releases/tag/1.2.7
generic

Release [Security Update] Roundcube Webmail 1.1.10 · roundcube/roundcubemail · GitHub

https://github.com/roundcube/roundcubemail/releases/tag/1.1.10
generic

File Disclosure Vulnerability · Issue #6026 · roundcube/roundcubemail · GitHub

https://github.com/roundcube/roundcubemail/issues/6026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturoundcube-sqlite3 (1.2~beta+dfsg.1-0ubuntu1+esm5) @ xenial2026-07-27ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 59× in last 7d / 344× 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 733 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCropbear/CVE-2017-16651
    First seen Jan 6, 2021

    Python implementation of Roundcube LFI (CVE-2017-16651)

    Open source ↗
  • Metasploitauxiliary/gather/roundcube_auth_file_read✓ verified
    First seen Nov 9, 2017

    Roundcube TimeZone Authenticated File Disclosure

    Open source ↗

Frequently asked(6)

What is CVE-2017-16651?
CVE-2017-16651 is a critical vulnerability published on November 9, 2017. Roundcube Webmail before 1.1.10, 1.2.x before 1.2.7, and 1.3.x before 1.3.3 allows unauthorized access to arbitrary files on the host's filesystem, including configuration files, as exploited in the wild in November 2017. The attacker must be able to authenticate at the target system with a valid…
When was CVE-2017-16651 disclosed?
CVE-2017-16651 was first published in the National Vulnerability Database on November 9, 2017, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16651 actively exploited?
Yes. CISA added CVE-2017-16651 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Roundcube Roundcube Webmail. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-16651?
CVE-2017-16651 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2017-16651?
CVE-2017-16651 affects Roundcube Roundcube Webmail. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2017-16651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16651, 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

Explore the affected products and dependency analysis for CVE-2017-16651

Explore →

Is Your Infrastructure Affected by CVE-2017-16651?

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