Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain write access to shared CalDAV calendar
-
DeliveryPlant event with malicious file:// ATTACH URI
-
ExploitVictim's client opens and saves the event
-
ExecutionEDS reads and base64-encodes targeted local file
-
ImpactEncoded file uploaded to server for attacker retrieval
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three concrete conditions: (1) the victim uses evolution-data-server with a shared/subscribed CalDAV calendar; (2) the attacker has write access to that shared calendar to inject an event whose ATTACH property holds a file:// URI; and (3) the victim interacts with the event such that it is saved, triggering EDS to read, base64-encode, and re-upload the referenced local file. The root cause is the absence of any file-path restriction or any check that an attachment originated from the server rather than being locally injected. Limiting factors that reduce real-world risk: authentication/write access to the shared calendar is needed (PR:L), user interaction is required (UI:R), and only files readable by the victim's user account can be exfiltrated (no privilege escalation). It does not affect integrity or availability. |
| Impact | This is a genuine but moderate-priority information-disclosure flaw, not a drop-everything issue. The supplied CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N) describes a network-reachable but authenticated (PR:L) attack that additionally requires victim interaction (UI:R) and yields high confidentiality impact with no integrity or availability effect - consistent with CWE-200. There is NO CISA KEV listing and NO public exploit referenced in the input, so exploitation status is 'no public exploit identified at time of analysis'; EPSS was not provided, so exploitation probability cannot be quantified. No SSVC decision data was supplied. The practical constraints are meaningful: the attacker must already have write access to a calendar the victim subscribes to (a shared CalDAV calendar) and the victim must interact with the malicious event, which makes this a targeted-abuse scenario rather than mass, unauthenticated internet exploitation. One data conflict to flag: the vector AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N computes to a CVSS 3.1 base score of 6.5, but the input states 5.7 - the numeric score and vector do not reconcile, so verify the authoritative score/vector with Red Hat/NVD. |
| Exploit ScenarioDerived | An attacker with write access to a CalDAV calendar that the victim subscribes to creates a calendar event whose ATTACH property contains a file:// URI pointing to a sensitive local file (e.g. file:///home/user/.ssh/id_rsa). When the victim's evolution-data-server processes and saves the event, it silently reads that local file, base64-encodes it, and uploads it as an attachment back to the shared server where the attacker can retrieve it. No public proof-of-concept exploit is referenced in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Arbitrary local file exfiltration is possible in evolution-data-server (EDS) when a calendar event's ATTACH property contains a file:// URI: on saving the event, EDS reads the referenced local file, base64-encodes it, and uploads it back to the calendar server. Exploitation requires an authenticated attacker with write access to a shared or subscribed CalDAV calendar (CVSS PR:L) plus the victim interacting with the malicious event (UI:R), and is limited to files readable by the victim's own account - confidentiality is the only impacted property (CVSS 5.7, CWE-200). No public exploit code has been identified at time of analysis, and the flaw is rated a moderate-priority information-disclosure issue rather than an urgent one.
RemediationAI
No vendor-released patch has been identified at time of analysis, so remediation must begin with exposure reduction until an upstream fix appears in the GNOME GitLab issue 672 (https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/672) and in the Red Hat advisory (https://access.redhat.com/security/cve/CVE-2026-110777, Bugzilla 2552693). The most direct control is to stop granting write access to shared CalDAV calendars to anyone who is not fully trusted, and to unsubscribe EDS clients from calendars writable by third parties - effective, but it breaks legitimate collaborative calendar use and requires auditing existing sharing ACLs on the CalDAV server. Where the server is under your control, filter or reject calendar objects whose ATTACH property uses a file:// (or other local-scheme) URI at ingest, which blocks the injection vector entirely at the cost of rejecting some exotic but legitimate client-generated attachments. On the endpoint, confine evolution-data-server with an SELinux/AppArmor policy that denies it read access to sensitive paths (home-directory documents, SSH keys, credential stores) and tighten filesystem permissions on those files - this limits the blast radius rather than the attack itself, and can generate denials that must be tuned to avoid breaking legitimate attachment handling. Because the exfiltration occurs on the save action, instructing users not to open, accept, or re-save calendar invitations or events from untrusted shared calendars provides immediate but user-dependent protection, and monitoring outbound CalDAV PUT payloads for unexpectedly large attachments can surface attempted exfiltration.
Affected ProductsAI
The affected component is GNOME evolution-data-server, the CalDAV/calendar backend used by Evolution and other GNOME groupware clients, across the versions tracked by the referenced vendor advisories; no explicit CPE identifiers or a specific vulnerable-version range were supplied with this advisory, and downstream rebuilds shipped by distributions - notably Red Hat's packages, which are tracked in the Red Hat security advisory at https://access.redhat.com/security/cve/CVE-2026-110777 and Bugzilla issue 2552693 - inherit the behaviour wherever the EDS CalDAV attachment-save path is present. The upstream defect is recorded in the GNOME GitLab issue https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/672, which is the authoritative source for confirmed version coverage. Any environment that subscribes EDS to a shared or third-party-writable CalDAV calendar should be treated as potentially affected until version-specific confirmation is published; users without a shared/subscribed CalDAV calendar and without write access granted to others are not exposed by this attack path.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
evolution-data-server is the GNOME backend daemon that stores and synchronises calendar, contact and mail data for clients such as Evolution, and it speaks the CalDAV protocol for remote calendar subscriptions. The iCalendar data model (RFC 5545) defines an ATTACH property that may reference either an inline binary payload or an external URI; EDS implements the URI form without validating the scheme, so a file:// URI is dereferenced directly on the local filesystem. The root cause class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): there is no file-path restriction or allow-list on ATTACH targets, and there is no provenance check distinguishing an attachment that legitimately came from the server from one injected locally by another calendar writer. Because the daemon treats any stored attachment as authoritative server state, it re-serialises the base64-encoded file contents back into the calendar object during save, turning the CalDAV channel into a one-way exfiltration path. The assessed vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N) reflects low attack complexity but a requirement for calendar write privileges and a user save/interaction step; there is no privilege escalation beyond the victim's own file-read permissions, and no integrity or availability impact.
Know when Gnome gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Attacker needs write access to a shared CalDAV calendar (PR:L) and the victim must save the event (UI:R); impact is file disclosure only, so C:H, I:N, A:N.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in evolution-data-server. Calendar events containing a file:// URI in their ATTACH property automatically read the targeted local file, base64-encode its contents and upload it back to the server when the event is saved. There are no file path restrictions or checks to verify whether the attachment originally came from the server or was added locally. This allows an attacker with access to a shared CalDAV calendar to exfiltrate arbitrary files the user has access to when interacting with malicious calendar events.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
backend/comics/comics-document.c (aka the comic book backend) in GNOME Evince before 3.24.1 allows remote attackers to e
Network Manager VPNC plugin (aka networkmanager-vpnc) before version 1.2.6 is vulnerable to a privilege escalation attac
gio/gsocks4aproxy.c in GNOME GLib before 2.82.1 has an off-by-one error and resultant buffer overflow because SOCKS4_CON
Multiple integer overflows in the (1) vnc_connection_server_message and (2) vnc_color_map_set functions in gtk-vnc befor
GNOME OCRFeeder before 0.8.4 allows OS command injection via shell metacharacters in a PDF or image filename. Rated crit
libsoup from versions 2.65.1 until 2.68.1 have a heap-based buffer over-read because soup_ntlm_parse_challenge() in soup
Gnome Pango 1.42 and later is affected by: Buffer Overflow. Rated critical severity (CVSS 9.8), this vulnerability is re
In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference. Rated critical sev
Heap-based buffer overflow in GLib's g_escape_uri_string() function allows local attackers to achieve high-integrity and
An exploitable heap overflow vulnerability exists in the gdk_pixbuf__jpeg_image_load_increment functionality of Gdk-Pixb
Eye of GNOME (aka eog) 3.16.5, 3.17.x, 3.18.x before 3.18.3, 3.19.x, and 3.20.x before 3.20.4, when used with glib befor
An exploitable integer overflow vulnerability exists in the tiff_image_parse functionality of Gdk-Pixbuf 2.36.6 when com
EUVD-2026-101521
GHSA-vfc3-547x-wpx2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB