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.
CVE-2026-2604
Score 5.6 from GitHub Security Advisory published 2026-06-17. a secondary CVSS source baseline 5.6; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- 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 computedSeverity56% × 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(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[SECURITY] [DLA 4503-1] evolution-data-server security update
https://lists.debian.org/debian-lts-announce/2026/03/msg00007.html(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/6272440301 – (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=2440301Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libedataserverui4-dev (3.56.2-3ubuntu0.1) @ questing | 2026-08-24 | ubuntu |
| ubuntu | libedataserverui1.2-dev (3.36.5-0ubuntu1+esm1) @ focal | 2026-08-24 | ubuntu |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| evolution-data-server | 3.38.3-1, 3.38.3-1+deb11u1, 3.38.3-1+deb11u2 | 3.38.3-1+deb11u3 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| evolution-data-server | 3.46.4-2 ... 3.56.2-8 (49 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| evolution-data-server | 3.56.1-2 ... 3.56.2-8 (10 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| evolution-data-server | 3.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 18× in last 7d / 96× 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 217 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:29 UTCEG score recompute
- 2026-08-24 22:29 UTCVendor advisory
- 2026-08-24 22:29 UTCGHSA enrichment
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 05:10 UTCEG score recompute
- 2026-08-23 05:10 UTCVendor advisory
- 2026-08-23 05:10 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 07:25 UTCEG score recompute
- 2026-08-21 07:25 UTCVendor advisory
- 2026-08-21 07:25 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 08:23 UTCEG score recompute
- 2026-08-20 08:23 UTCVendor advisory
- 2026-08-20 08:23 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 08:16 UTCEG score recompute
- 2026-08-19 08:16 UTCVendor advisory
- 2026-08-19 08:16 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:41 UTCEG score recompute
- 2026-08-17 07:41 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-17 07:41 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:39 UTCEG score recompute
- 2026-08-16 08:39 UTCVendor advisory
- 2026-08-16 08:39 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 09:41 UTCEG score recompute
- 2026-08-15 09:41 UTCVendor advisory
- 2026-08-15 09:41 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:25 UTCEG score recompute
- 2026-08-14 09:25 UTCVendor advisory
- 2026-08-14 09:25 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 10:27 UTCEG score recompute
- 2026-08-13 10:27 UTCVendor advisory
- 2026-08-13 10:27 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 11:29 UTCEG score recompute
- 2026-08-12 11:29 UTCVendor advisory
- 2026-08-12 11:29 UTCGHSA enrichment
- 2026-08-11 12:30 UTCEG score recompute
- 2026-08-11 12:30 UTCVendor advisory
- 2026-08-11 12:30 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:32 UTCVendor advisory
- 2026-08-10 13:32 UTCGHSA enrichment
- 2026-08-09 14:30 UTCEG score recompute
- 2026-08-09 14:30 UTCVendor advisory
- 2026-08-09 14:30 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 15:31 UTCVendor advisory
- 2026-08-08 15:31 UTCGHSA enrichment
- 2026-08-07 16:33 UTCEG score recompute
- 2026-08-07 16:33 UTCVendor advisory
- 2026-08-07 16:33 UTCGHSA enrichment
- 2026-08-06 17:35 UTCEG score recompute
- 2026-08-06 17:35 UTCVendor advisory
- 2026-08-06 17:35 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 18:36 UTCVendor advisory
- 2026-08-05 18:36 UTCGHSA enrichment
- 2026-08-04 15:29 UTCEG score recompute
- 2026-08-04 15:29 UTCVendor advisory
- 2026-08-04 15:29 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 08:48 UTCVendor advisory
- 2026-08-03 08:48 UTCGHSA enrichment
- 2026-08-02 06:58 UTCEG score recompute
- 2026-08-02 06:58 UTCVendor advisory
- 2026-08-02 06:58 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 08:00 UTCEG score recompute
- 2026-08-01 08:00 UTCVendor advisory
- 2026-08-01 08:00 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 04:00 UTCEG score recompute
- 2026-07-31 04:00 UTCVendor advisory
- 2026-07-31 04:00 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 03:48 UTCEG score recompute
- 2026-07-30 03:47 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 02:28 UTCEG score recompute
- 2026-07-29 02:28 UTCVendor advisory
- 2026-07-29 02:27 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 18:17 UTCEG score recompute
- 2026-07-27 18:17 UTCGHSA enrichment
- 2026-07-26 19:18 UTCEG score recompute
- 2026-07-26 19:18 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-2604?
When was CVE-2026-2604 disclosed?
Is CVE-2026-2604 actively exploited?
What is the CVSS score of CVE-2026-2604?
How do I remediate CVE-2026-2604?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2604
Is Your Infrastructure Affected by CVE-2026-2604?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.