CVE-2026-21437

eopkg vulnerable to package file list integrity bypass

Published Jan 1, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
Description
eopkg is a Solus package manager implemented in python3. In versions prior to 4.4.0, a malicious package could include files that are not tracked by `eopkg`. This requires the installation of a package from a malicious or compromised source. Files in such packages would not be shown by `lseopkg` and related tools. The issue has been fixed in v4.4.0. Users only installing packages from the Solus repositories are not affected.

Analysis

AI-generated

Technical impact

A malicious package can include files that are not recorded by the eopkg package manager. This bypasses the integrity mechanism that tracks installed files, allowing files to exist on the system without being listed by tools such as lseopkg. The vulnerability is a CWE-353 scenario where an attacker can deliver hidden files that evade standard package management tracking, potentially compromising system integrity and making removal or auditing difficult.

Affected Systems

Versions of eopkg older than 4.4.0, bundled with Solus, are affected. The package manager is implemented in Python3, and only installations from the official Solus repositories are safe. Users who install packages from other sources may be impacted.

Risk and Exploitability

The CVSS score is 2, indicating low severity. The EPSS score is below 1%, showing a very low probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Attackers can exploit it by installing a malicious or compromised package from an untrusted source, which requires local installation privileges or the ability to place a crafted package in a repository. Because the flaw only manifests during package installation and the fix appears in v4.4.0, the current risk to users relying solely on official repositories is minimal, but the risk rises if third‑party packages are used.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade eopkg to version 4.4.0 or later to apply the fixed integrity check.
  • Reinstall or remove any packages that were installed from untrusted or third‑party sources, and verify that all installed files are now tracked by eopkg tools.
  • Ensure that future package installations are sourced only from the official Solus repository to prevent similar integrity bypass attempts.

Generated by OpenCVE AI on April 18, 2026 at 08:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Getsol
Getsol eopkg
CPEs cpe:2.3:a:getsol:eopkg:*:*:*:*:*:python:*:*
Vendors & Products Getsol
Getsol eopkg
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description eopkg is a Solus package manager implemented in python3. In versions prior to 4.4.0, a malicious package could include files that are not tracked by `eopkg`. This requires the installation of a package from a malicious or compromised source. Files in such packages would not be shown by `lseopkg` and related tools. The issue has been fixed in v4.4.0. Users only installing packages from the Solus repositories are not affected.
Title eopkg vulnerable to package file list integrity bypass
Weaknesses CWE-353
References
Metrics cvssV4_0

{'score': 2, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:H'}

Weaknesses
  • CWE-353

    Missing Support for Integrity Check

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jan 2, 2026, 6:54 PM
Reserved
Dec 29, 2025, 3:00 AM
Status
Analyzed
Published
Jan 1, 2026, 6:15 PM
Modified
Jun 17, 2026, 10:18 AM