CVE-2026-88859VulnerabilityPublished 09/10/2026Updated 10/17/2026

A flaw was found in Evolution. A remote attacker can exploit this vulnerability by sending a specially crafted HTML email containing a spoofed vCard… (CVE-2026-88859)

Affects evolutionSource GCVE Database

ghsa-8j98-q77q-pmv2

Not known to be exploited · CVSS 6.3 Medium.

Data as of 10/25/2026, 16:58:58 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu:16.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=xenial`Other threats	Affected =3.16.5-1ubuntu3 =3.18.1-1ubuntu2 =3.18.2-0ubuntu1 =3.18.2-0ubuntu2 =3.18.3-0ubuntu1 =3.18.3-1ubuntu1 =3.18.4-0ubuntu1 =3.18.5-1ubuntu1 =3.18.5.1-1ubuntu1 =3.18.5.2-0ubuntu1 =3.18.5.2-0ubuntu3 =3.18.5.2-0ubuntu3.1 =3.18.5.2-0ubuntu3.2	Fixed in–
Ubuntu:18.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=bionic`Other threats	Affected =3.26.1-1 =3.26.2-1 =3.26.2-1ubuntu1 =3.26.3-1 =3.26.5-1 =3.26.5-1build1 =3.27.90-1 =3.28.0-1 =3.28.0-4 =3.28.1-1 =3.28.1-2 =3.28.5-0ubuntu0.18.04.1 =3.28.5-0ubuntu0.18.04.2	Fixed in–
Ubuntu:20.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=focal`Other threats	Affected =3.34.1-2 =3.34.1-2build1 =3.34.1-3 =3.34.1-4 =3.35.91-1 =3.35.92-1 =3.36.0-1 =3.36.1-1 =3.36.1-2 =3.36.2-0ubuntu1 =3.36.3-0ubuntu1 =3.36.4-0ubuntu1 =3.36.5-0ubuntu1	Fixed in–
Ubuntu:22.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=jammy`Other threats	Affected =3.40.4-1 =3.42.0-2 =3.42.1-1 =3.42.2-1 =3.42.3-1 =3.43.3-1 =3.44.0-1 =3.44.0-1ubuntu1 =3.44.1-0ubuntu1 =3.44.4-0ubuntu1 =3.44.4-0ubuntu2 =3.44.4-0ubuntu2.1	Fixed in–
Ubuntu:24.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=noble`Other threats	Affected =3.50.0-1 =3.50.1-1 =3.50.2-1 =3.50.3-1 =3.52.0-1build1 =3.52.0-1build2 =3.52.3-0ubuntu1 =3.52.3-0ubuntu1.1	Fixed in–
Ubuntu:26.10evolution`pkg:deb/ubuntu/evolution?arch=source&distro=stonking`Other threats	Affected =3.56.2-9 =3.56.2-10 =3.56.2-10build1	Fixed in–
Ubuntu:26.04:LTSevolution`pkg:deb/ubuntu/evolution?arch=source&distro=resolute`Other threats	Affected =3.56.2-4 =3.56.2-5 =3.56.2-7 =3.56.2-8 =3.56.2-9	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a patch is available, users should exercise caution when interacting with emails containing vCard controls, especially from untrusted sources.

Description

A vulnerability in Evolution allows a remote attacker to execute arbitrary JavaScript by sending a specially crafted HTML email containing a spoofed vCard control. When the victim clicks the control, Evolution's JavaScript handler incorrectly assigns an attacker-controlled URL to an iframe, bypassing script execution protections. This can lead to arbitrary code execution within the mail-viewing context. The vulnerability has a CVSS score of 6.3 (medium severity).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript code within the context of the email client, potentially leading to information disclosure, manipulation of email content, or other actions permitted by script execution in the mail-viewing context. The impact is limited by the need for user interaction (clicking the spoofed vCard control).

Weaknesses

CWE-84Improper Neutralization of Encoded URI Schemes in a Web Page (opens in a new tab)
Variant weakness
The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.
Implementation · Input Validation
Resolve all URIs to absolute or canonical representations before processing.
Implementation · Input Validation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including tag attributes, hidden fields, cookies,…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…