Cyber Resilience

CVE-2026-21437

Getsol Eopkg ≤ 4.4.0

Published
01 January 2026
Modified
04 March 2026
Patch / advisory
CVSS Score v4 2.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0015 5th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-21437 is a low-severity Missing Support for Integrity Check (CWE-353) vulnerability in Getsol Eopkg. Its CVSS base score is 2.0 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Component Firmware (T1542.002); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1542.002 Component Firmware Stealth
Adversaries may modify component firmware to persist on systems.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-21436Same product: Getsol Eopkg
CVE-2025-48811Shared CWE-353
CVE-2025-32882Shared CWE-353
CVE-2025-48500Shared CWE-353
CVE-2023-32475Shared CWE-353
CVE-2026-17583Shared CWE-353
CVE-2025-15364Shared CWE-353
CVE-2025-32890Shared CWE-353
CVE-2024-46917Shared CWE-353
CVE-2026-3856Shared CWE-353

Affected Assets

getsol
eopkg
≤ 4.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V12.1.1
  • V17.2.2
  • V17.2.5
  • V17.2.8

Mitigating Controls (NIST 800-53 r5) AI

SC-8 directly requires mechanisms to protect integrity of transmitted data, which structurally eliminates the missing checksum weakness in protocols.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-02 full match
prevents

Directly requires integrity protection for data-in-transit via checksums or equivalent mechanisms.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Cryptographic controls can provide integrity verification for transmitted data.

mitigates

Network security controls can mandate integrity mechanisms on transmission protocols.

prevents

Security requirements for network services can require integrity checks on data in transit.

prevents

Application security requirements can specify integrity checks for data transmission.

prevents

Secure architecture principles can mandate integrity protection for communications.

prevents

Secure coding standards can require integrity verification mechanisms in protocols.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-353
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-353
  • V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-353
RHEL 8 (1 rule)
  • V-230487 RHEL 8 must not have the telnet-server package installed. prevents CWE-353

References