rootpwn

critical · CVSS v3 8.1 · CVSS v4 7

CVE-2026-93992

Gopeed 2.0.0-beta.3 contains a path traversal flaw in its archive extraction routine that lets an attacker write files outside the intended

Overview

Gopeed 2.0.0-beta.3 contains a path traversal flaw in its archive extraction routine that lets an attacker write files outside the intended directory. The vulnerability is triggered when users enable AutoExtract and download malicious archives. It can be exploited to overwrite system files or drop malicious payloads.

Description

Gopeed through 2.0.0-beta.3 contains a path traversal vulnerability in archive extraction that allows attackers to write arbitrary files outside the extraction directory. Attackers can craft malicious archives with entries containing directory traversal sequences that bypass validation, enabling file write operations when users download and extract archives with AutoExtract enabled.

Impact

The flaw compromises confidentiality, integrity, and availability by allowing attackers to place arbitrary files on the host. End‑users and administrators of Gopeed installations are directly impacted, as the vulnerability can be triggered without user interaction beyond enabling AutoExtract.

Remediation

Update to the latest Gopeed release that patches the extraction logic. If an update is not immediately possible, disable AutoExtract or configure the application to reject archives containing directory traversal sequences. Additionally, enforce strict file‑system permissions and validate extraction paths server‑side.

Risk context

The CVSS v3 score of 8.1 and critical severity indicate a high‑risk vulnerability. With no EPSS data, defenders should treat this as an urgent issue and prioritize remediation.

Affected products

  • Gopeed 2.0.0-beta.3
  • Gopeed 2.0.0-beta

Scores

Severity
critical
CVSS v2
9.4
CVSS v3
8.1
CVSS v4
7
EPSS
—

path-traversal archive-extraction Gopeed critical file-write autoextract defense

← All CVEs

Related CVEs

critical

CVE-2026-93958

A vulnerability was found in D-Link R95 BE9500_1.00.16. This vulnerability affects the function system of the file /bin/ssi of the component DHMAPI. The manipulation of the argument NTPServer results in os command injection. The attack can be executed remotely. The exploit has been made public and could be used.

View analysis

critical

CVE-2026-94083

Suricata before 8.0.7 has a DoH2 type confusion that can cause an invalid free, because cleanup code for the HTTP2 state is executed even though the actual state is HTTP1 (when there is a DoH2 request with an HTTP1 to HTTP2 upgrade). This requires app-layer.protocols.doh2 to be enabled, which is the default in 8.x versions.

View analysis

critical

CVE-2026-94084

Suricata IDS/IPS versions prior to 8.0.7 are vulnerable to a use‑after‑free in the Http2ThreadMultiBuf component when rules inspect http.response_header, potentially causing a crash or memory corruption. This flaw can disrupt IDS operation and may allow attackers to force a denial of service. The issue is critical with a CVSS v3 score of 9.4.

View analysis

critical

CVE-2026-78030

DBI versions before 1.653 for Perl load arbitrary modules via unvalidated dbm_type and dbm_mldbm attributes in DBD::DBM. DBD::DBM passes the dbm_type and dbm_mldbm connect attributes to require without checking that the value names a module. require treats a path-shaped string as a literal filename and does not consult @INC, so the attribute chooses the file that Perl loads and runs. The MLDBM::Serializer:: prefix that DBD::DBM prepends to dbm_mldbm is not a boundary: only the :: separators are rewritten to /, so a value containing / traverses out of the serializer directory. The value is also assigned to $MLDBM::Serializer, which MLDBM requires the same way when it ties the table. A caller that lets an untrusted party influence either attribute, for example through a DSN fragment or a parameter that selects a storage backend, runs the file-scope code of whatever module the value names. For example, my $dsn = "dbi:DBM:f_dir=/var/db;dbm_type=../../Untrusted.pm" my $dbh = DBI->connect( $dsn ); Note that DBD::Gofer forwards connect attributes to the server side, and DBI::ProxyServer checks only that a DSN starts with a driver prefix.

View analysis