CVE-2026-2604

MEDIUMPre-NVD 5.65.6
EchelonGraph scoreMEDIUM confidence

Score 5.6 from GitHub Security Advisory published 2026-06-17. a secondary CVSS source baseline 5.6; sources differ by 0.0.

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

A fix is available — apply it.

A flaw was found in evolution-data-server. Inconsistent comparison logic in the addressbook file backend allows a Flatpak application with D-Bus access to craft a malicious URI containing directory traversal sequences. This URI is stored without proper validation during contact creation or modification. Later, during contact deletion, the URI is processed with a less strict check, leading to the deletion of arbitrary files on the host filesystem. This could potentially include critical Flatpak override files.

CVSS v3
5.6
EG Score
5.6(medium)
EG Risk
30(Track)
EG Risk 30/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
Severity56% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jun 18, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available

(CVE-2026-2604) Canonicalize path before local cache file removal (#627) · Issues · GNOME / evolution-data-server · GitLab

https://gitlab.gnome.org/GNOME/evolution-data-server/-/work_items/627
generic Patch Available

[SECURITY] [DLA 4503-1] evolution-data-server security update

https://lists.debian.org/debian-lts-announce/2026/03/msg00007.html
generic🟡 PoC Available

(CVE-2026-2604) Canonicalize path before local cache file removal (#627) · Issues · GNOME / evolution-data-server · GitLab

https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/627
redhat

2440301 – (CVE-2026-2604) CVE-2026-2604 evolution-data-server: Evolution Data Server: Arbitrary file deletion via inconsistent URI handling

https://bugzilla.redhat.com/show_bug.cgi?id=2440301
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-2604

Vendor Advisories for CVE-2026-2604(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibedataserverui4-dev (3.56.2-3ubuntu0.1) @ questing2026-09-14ubuntu
ubuntulibedataserverui1.2-dev (3.36.5-0ubuntu1+esm1) @ focal2026-09-14ubuntu

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
evolution-data-server3.38.3-1, 3.38.3-1+deb11u1, 3.38.3-1+deb11u23.38.3-1+deb11u3
Debian:12(1)
PackageVulnerable rangeFixed inDependents
evolution-data-server3.46.4-2 ... 3.56.2-8 (49 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
evolution-data-server3.56.1-2 ... 3.56.2-8 (10 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
evolution-data-server3.56.1-2 ... 3.56.2-7 (8 versions)3.56.2-8

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 9× in last 7d / 42× 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 245 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-2604?
CVE-2026-2604 is a medium vulnerability published on June 17, 2026. A flaw was found in evolution-data-server. Inconsistent comparison logic in the addressbook file backend allows a Flatpak application with D-Bus access to craft a malicious URI containing directory traversal sequences. This URI is stored without proper validation during contact creation or…
When was CVE-2026-2604 disclosed?
CVE-2026-2604 was first published in the National Vulnerability Database 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-2604 actively exploited?
CVE-2026-2604 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 91.1% of all scored CVEs.
What is the CVSS score of CVE-2026-2604?
CVE-2026-2604 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2026-2604?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2604, 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-2604

Explore →

Is Your Infrastructure Affected by CVE-2026-2604?

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