CVE-2010-4226: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.9% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 2014
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
To mitigate CVE-2010-4226, European organizations should: 1) Identify and inventory all systems using vulnerable versions of cpio, especially those involved in RPM package extraction. 2) Upgrade cpio to versions where this vulnerability is fixed or use alternative, secure extraction tools that properly validate symlinks within archives. 3) Implement strict controls on RPM package sources, ensuring only trusted and verified packages are used, employing cryptographic signature verification to prevent malicious package introduction. 4) Restrict extraction operations to non-privileged users or sandboxed environments to limit the impact of potential exploitation. 5) Monitor file system integrity on critical systems to detect unauthorized file modifications indicative of exploitation attempts. 6) Incorporate security scanning in build and deployment pipelines to detect malicious or malformed RPM packages. 7) Educate system administrators about the risks of extracting untrusted RPMs and enforce policies to avoid such practices. These targeted measures go beyond generic advice by focusing on controlling the attack vector (RPM package handling), privilege restrictions, and proactive detection.
Description
cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.
References
- support.novell.com/security/cve/CVE-2010-4226.html (opens in a new tab)
- lists.opensuse.org/opensuse-security-announce/2011-04/msg00000.html (opens in a new tab)
- bugzilla.novell.com/show_bug.cgi?id=665768 (opens in a new tab)
- lists.opensuse.org/opensuse-updates/2011-03/msg00008.html (opens in a new tab)