Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim into installing crafted .xpi in Epiphany
-
Deliverylibarchive extracts TAR-as-xpi via format_all
-
ExploitTAR hard-link entry resolves to victim's existing file
-
Executionarchive_write_disk truncates target with ARCHIVE_EXTRACT_PERM
-
ImpactVictim file overwritten with attacker content and mode
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires the victim to actively install or open an attacker-crafted .xpi WebExtension in Epiphany 47.0 or later, where the installer used archive_read_support_format_all() and thus accepts a TAR file renamed to .xpi rather than a real ZIP. The malicious archive must contain a hard-link entry whose target is an existing, user-writable file that the attacker wishes to overwrite, and extraction runs with archive_write_disk options including ARCHIVE_EXTRACT_PERM so the file's content and mode bits are replaced. Limiting factors: mandatory user interaction (the victim must install/open the package), local delivery of the file, no warning dialog making social engineering easier but still requiring a deliberate install action, and the affected version range (>= 47.0); it is resolved by the fix that enables only ZIP format support. |
| Impact | This is a moderate, user-interaction-gated integrity flaw, not a mass-exploitation priority. The supplied CVSS:3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, base 5.5) is internally consistent with the description: exploitation is local and requires the victim to actively install or open a malicious .xpi, which is why the vector is AV:L with UI:R rather than a remote drive-by. The sole high-rated impact is integrity (I:H) - an attacker-chosen existing user-writable file is truncated and overwritten with attacker-controlled content and mode bits - with no confidentiality (C:N) or availability (A:N) impact claimed. There is no EPSS score in the supplied data, so exploitation-probability cannot be quantified. This is NOT on CISA KEV, and no proof-of-concept or exploit reference is present - the only links are the Red Hat tracker, the GNOME work item, and the fix merge request. The vuln.today decision label is 'this_month', i.e. a planned-patch priority rather than act_now/emergency, which aligns with the local vector plus mandatory user interaction. The main reason this is more than theoretical is that it needs no special configuration and no warning dialog is shown, but the local-plus-user-interaction requirement keeps real-world risk contained. Note the signals are coherent (no KEV/POC, local vector, moderate CVSS, 'this_month' label all agree) rather than conflicting. |
| Exploit ScenarioDerived | An attacker crafts a TAR archive renamed to a .xpi WebExtension package containing a hard-link entry whose target is an existing user-writable file in the victim's home directory. The attacker delivers it (e.g. via a download link or email) and socially engineers the victim into installing or opening it in Epiphany 47.0 or later; libarchive's format-agnostic extraction accepts the TAR, follows the hard link, and silently truncates and overwrites the targeted file with attacker-controlled content and mode bits. No public exploit is identified at time of analysis, though the trigger mechanism is fully documented in the upstream report. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Arbitrary file overwrite in GNOME Epiphany 47.0 and later allows an attacker-crafted WebExtension package to truncate and replace an existing user-writable file with attacker-controlled content and permission bits. The installer in src/webextension/ephy-web-extension-manager.c used libarchive with archive_read_support_format_all(), so a TAR archive renamed to *.xpi was accepted instead of only genuine ZIP files; a hard-link entry inside that TAR, combined with archive_write_disk options including ARCHIVE_EXTRACT_PERM, redirects the write onto an attacker-chosen existing file. The victim must deliberately install or open the malicious .xpi (UI:R, local delivery), severity is assessed at CVSS 5.5 with integrity-only impact, and no public exploit was identified at time of analysis; an upstream fix restricting the installer to ZIP format only has been merged but a tagged patched release is not confirmed in the available data.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed. The corrective change is merge request !2248 (commit 0cc9ab55), which restricts the WebExtension installer to ZIP format support only, so TAR and other libarchive-auto-detected containers are no longer extracted; apply that commit or upgrade Epiphany to a build that includes it, referencing https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/2248 and the upstream work item https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2988, with distribution status tracked at https://access.redhat.com/security/cve/CVE-2026-118599 and https://bugzilla.redhat.com/show_bug.cgi?id=2562969. Until a patched package is installed, the exposure is governed entirely by the install action: do not install or open .xpi WebExtension packages from untrusted or unverified sources, since successful exploitation needs the victim to deliberately install or open the crafted file - the trade-off is that this blocks legitimate third-party extension installation rather than selectively filtering hard-link TAR payloads, because the affected code path provides no warning dialog to distinguish them.
Affected VersionsENISA
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
Epiphany's WebExtension installation path parses .xpi packages through libarchive. Because decompress_xpi_thread() called archive_read_support_format_all() together with the filter set, the reader auto-detected format rather than enforcing ZIP, so any libarchive-supported container - notably TAR - was accepted under an .xpi filename. TAR supports hard-link entry types, and the extraction side used archive_write_disk with options that include ARCHIVE_EXTRACT_PERM, meaning the writer follows the link target and applies the archived content and mode bits to it. The result is a CWE-59 improper-link-resolution class flaw: instead of creating an isolated extraction tree the writer can be steered onto a pre-existing, user-writable file that the attacker wants replaced. The impact is integrity-only (I:H, C:N/A:N) and requires the user to install or open the crafted package, which is why the vector is AV:L/AC:L/PR:N/UI:R. This is distinct from the earlier ZIP-slip path traversal tracked as CVE-2026-77679 (#2922 / MR !2143): that issue concerned traversal in ZIP member paths, whereas this one abuses container-format auto-detection plus hard-link semantics. The fix (MR !2248, commit 0cc9ab55) simply enables ZIP format support only, removing TAR and other formats from the accepted set.
Know when Epiphany 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:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Local crafted .xpi must be deliberately installed/opened by the user (AV:L, UI:R); no privileges required (PR:N); arbitrary user-file overwrite gives I:H with no confidentiality or availability impact.
Primary rating from Vendor (fedora).
CVSS VectorVendor: fedora
DescriptionCVE.org
A file overwrite vulnerability exists in Epiphany when installing WebExtension packages from .xpi files.
In src/webextension/ephy-web-extension-manager.c, decompress_xpi_thread() used libarchive with archive_read_support_format_all() (and filters), so the installer did not require a real ZIP. A TAR file named *.xpi was extracted. TAR supports hard-link entry types; with Epiphany's archive_write_disk options (including ARCHIVE_EXTRACT_PERM), a crafted hard-link target can cause an attacker-chosen existing user-writable file to be truncated and overwritten with attacker-controlled content and mode bits, without a dedicated warning dialog, when the user installs or opens the crafted .xpi.
This is related to but separate from the ZIP-slip path traversal fixed as CVE-2026-77679 (#2922 / MR !2143).
Requirements: the victim must install or open a malicious WebExtension (.xpi).
Affected: Epiphany >= 47.0 (WebExtension XPI install path). Fixed: https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/2248 (commit 0cc9ab55 - only enable ZIP format support). Upstream: https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2988 Reporter acknowledgment: Fernando Munoz
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnerable to address bar spoofing upon certain JavaScript redirect
In Epiphany (aka GNOME Web) through 43.0, untrusted web content can trick users into exfiltrating passwords, because aut
libephymain.so in GNOME Web (aka Epiphany) through 3.28.2.1 allows remote attackers to cause a denial of service (applic
ephy-session.c in libephymain.so in GNOME Web (aka Epiphany) through 3.28.2.1 allows remote attackers to cause a denial
XSS can occur in GNOME Web (aka Epiphany) before 40.4 and 41.x before 41.1 via an error page. Rated medium severity (CVS
XSS can occur in GNOME Web (aka Epiphany) before 40.4 and 41.x before 41.1 when View Source mode or Reader mode is used,
XSS can occur in GNOME Web (aka Epiphany) before 40.4 and 41.x before 41.1 because a server's suggested_filename is used
XSS can occur in GNOME Web (aka Epiphany) before 40.4 and 41.x before 41.1 via an about: page, as demonstrated by ephy-a
GNOME Web (Epiphany) 3.23 before 3.23.5, 3.22 before 3.22.6, 3.20 before 3.20.7, 3.18 before 3.18.11, and prior versions
In GNOME Epiphany before 41.4 and 42.x before 42.2, an HTML document can trigger a client buffer overflow (in ephy_strin
Epiphany (GNOME Web) 45.0 through 51.x writes a stored PERMIT for both the webcam and microphone permission of a site or
EUVD-2026-114699
GHSA-h27g-h5mg-6hm2
NVD
CVE.org
EPSS
Exploit-DB