Evolution-data-server: evolution data server: arbitrary file deletion via inconsistent uri handling
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.
- Published
- Jun 17, 2026
- Updated
- Sep 25, 2026
- EPSS
- 0.3% · 19th percentile
- CWE
- CWE-73
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 5.6
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
GNOME Evolution Data Server
- before 3.59.3affected · semver
Red Hat Red Hat Enterprise Linux 10
- all versionsaffected
Red Hat Red Hat Enterprise Linux 6
- all versionsaffected
Red Hat Red Hat Enterprise Linux 7
- all versionsaffected
Red Hat Red Hat Enterprise Linux 8
- all versionsaffected
Red Hat Red Hat Enterprise Linux 9
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | evolution-data-server | before 3.38.3-1+deb11u3 | 3.38.3-1+deb11u3 |
| Debian:12 | evolution-data-server | before 3.46.4-2+deb12u1 | 3.46.4-2+deb12u1 |
| Debian:13 | evolution-data-server | all versions | — |
| Debian:14 | evolution-data-server | before 3.56.2-8 | 3.56.2-8 |
| openSUSE:Tumbleweed | evolution-data-server | before 3.58.3-2.1 | 3.58.3-2.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | evolution-data-server | before 3.42.5-150400.3.10.1 | 3.42.5-150400.3.10.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | evolution-data-server | before 3.50.3-150600.3.9.1 | 3.50.3-150600.3.9.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | evolution-data-server | before 3.50.3-150600.3.9.1 | 3.50.3-150600.3.9.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GNOME Evolution Data Server | 3.59.3 | Vendor (CNA) |
| debian:evolution-data-server | 3.46.4-2+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:evolution-data-server | 3.50.3-150600.3.9.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:evolution-data-server | 3.50.3-150600.3.9.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/security/cve/CVE-2026-2604
- bugzilla.redhat.com/show_bug.cgi?id=2440301
- gitlab.gnome.org/GNOME/evolution-data-server/-/issues/627
- lists.debian.org/debian-lts-announce/2026/03/msg00007.html
- lists.debian.org/debian-lts-announce/2026/09/msg00031.html
- gitlab.gnome.org/GNOME/evolution-data-server/-/work_items/627
Vendor advisories and official records. Exploit/PoC links are deliberately left out.