Untracked file installation via undeclared archive entries
Published Jan 1, 2026 · Updated Jan 1, 2026
Package file-list integrity bypass in Solus eopkg before 4.4.0 allows attackers to install untracked files via a crafted package. The archive extractor wrote entries absent from the package's declared file list, so the package database and lseopkg omitted them and removal left them behind. Exploitation requires a user to install a package from a malicious or compromised source; packages from Solus repositories are not affected.
Summary
What happened
Package file-list integrity bypass in Solus eopkg before 4.4.0 allows attackers to install untracked files via a crafted package. The archive extractor wrote entries absent from the package's declared file list, so the package database and lseopkg omitted them and removal left them behind. Exploitation requires a user to install a package from a malicious or compromised source; packages from Solus repositories are not affected.
The record
- CVE
- CVE-2026-21437
- Published
- Jan 1, 2026
- Updated
- Jan 1, 2026
- Vendor
- Solus
- Product
- eopkg
- Classifications
- CWE-353, T1195.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 1, 2026CVE publishedPublication date reported by the CVE source.
- Jan 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- nano-malicious eopkg test packageproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo