CVE-2026-25916

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-02-09. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 4.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Roundcube Webmail before 1.5.13 and 1.6 before 1.6.13, when "Block remote images" is used, does not block SVG feImage.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity43% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

February 9, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 9, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

Roundcube Webmail <1.5.13 / <1.6.13 allows attackers to force remote image loads via SVG feImage — NULL CATHEDRAL

https://nullcathedral.com/posts/2026-02-08-roundcube-svg-feimage-remote-image-bypass/
generic🔴 Active Exploitation

Roundcube Webmail: SVG feImage bypasses image blocking to track email opens | Hacker News

https://news.ycombinator.com/item?id=46937012
github_commit

commit 26d7677 (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit 26d7677 — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/26d7677

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturoundcube-sqlite3 (1.2~beta+dfsg.1-0ubuntu1+esm8) @ xenial2026-06-12ubuntu

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
roundcube1.4.11+dfsg.1-4 ... 1.4.15+dfsg.1-1~deb11u2~bpo10+1 (15 versions)1.4.15+dfsg.1-1+deb11u7—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
roundcube1.6.1+dfsg-1 ... 1.6.5+dfsg-1~deb12u1 (14 versions)1.6.5+dfsg-1+deb12u7—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
roundcube1.6.11+dfsg-1, 1.6.12+dfsg-0+deb13u1, 1.6.12+dfsg-11.6.13+dfsg-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
roundcube1.6.11+dfsg-1, 1.6.12+dfsg-11.6.13+dfsg-1—

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 6× in last 7d / 26× 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 200 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCmbanyamer/CVE-2026-25916-Roundcube-Webmail-DOM-based-XSS-Exploit-via-SVG-href-Attribute
    First seen Feb 9, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2026-25916?
CVE-2026-25916 is a medium vulnerability published on February 9, 2026. Roundcube Webmail before 1.5.13 and 1.6 before 1.6.13, when "Block remote images" is used, does not block SVG feImage.
When was CVE-2026-25916 disclosed?
CVE-2026-25916 was first published in the National Vulnerability Database on February 9, 2026, with the most recent update on June 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-25916 actively exploited?
CVE-2026-25916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.2% of all scored CVEs.
What is the CVSS score of CVE-2026-25916?
CVE-2026-25916 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-25916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25916, 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-25916

Explore →

Is Your Infrastructure Affected by CVE-2026-25916?

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

Start Free Scan →Browse All CVEs