Skip to main content
No exploitation reportedFix available

CVE-2019-14866

No exploitation reported by the sources we read.

  • Published2020-01-07
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives. When cpio is used to create TAR archives from paths an attacker can write to, the resulting archive may contain files with permissions the attacker did not have or in paths he did not have access to. Extracting those archives from a high-privilege user without carefully reviewing them may lead to the compromise of the system.

Timeline

dates in UTC
  1. 2020-01-0717:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-04 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-14866?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-14866?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Redhat enterprise linux
BranchAffectedFixed in
7.0= 7.0no fix published
8.0= 8.0no fix published
Gnu cpio
BranchAffectedFixed in
2.13< 2.132.13

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • cpioUbuntu:Pro:14.04:LTSall versions · fixed in 2.11+dfsg-1ubuntu1.2+esm1
  • cpioUbuntu:18.04:LTSall versions · fixed in 2.12+dfsg-6ubuntu0.18.04.1
  • cpioUbuntu:16.04:LTSall versions · fixed in 2.11+dfsg-5ubuntu1.1
  • cpioSUSE:Linux Enterprise Server for SAP Applications 12 SP5all versions · fixed in 2.11-36.6.1
  • cpioSUSE:Linux Enterprise Server for SAP Applications 12 SP4all versions · fixed in 2.11-36.6.1
  • cpioSUSE:Linux Enterprise Server 12 SP5all versions · fixed in 2.11-36.6.1
  • cpioSUSE:Linux Enterprise Server 12 SP4all versions · fixed in 2.11-36.6.1
  • cpioSUSE:Linux Enterprise Module for Basesystem 15 SP1all versions · fixed in 2.12-3.3.1

33 more package ranges on OSV.dev

Vendor advisories

  • CVE-2019-14866 Red Hat Product Security63 products fixed · 2 known affected

    cpio: improper input validation when writing tar header fields leads to unexpected tar generation

    cpio as a component of Red Hat Enterprise Linux 5 · cpio as a component of Red Hat Enterprise Linux 6

  • SSA-202008 Siemens ProductCERT11 known affected

    SSA-202008: Multiple Vulnerabilities in Ruggedcom Rox Before V2.17.0

    RUGGEDCOM ROX MX5000 · RUGGEDCOM ROX MX5000RE · RUGGEDCOM ROX RX1400 · +8 more

  • RHSA-2022:0073 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: cpio security update

  • RHSA-2021:1582 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: cpio security update

  • RHSA-2021:0949 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat OpenShift Do openshift/odo-init-image 1.1.3 security update

  • RHSA-2020:3908 Red Hat Product Security18 products fixed

    Red Hat Security Advisory: cpio security update

Full record on NVD

Fix

  1. Vendor fix Siemens ProductCERT SSA-202008 · 11 productsUpdate to V2.17.0 or later version
  2. Vendor fix Red Hat Product Security RHSA-2022:0073 · 13 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2021:0949 · 1 productDownload and install a new CLI binary by following the instructions linked from the References section.
  4. Workaround from the vendor Red Hat Product Security RHSA-2022:0073 · 13 productsTAR archives should be inspected before being extracted and the extraction should be performed with the `tar` command or `--no-absolute-filenames` option if done with `cpio`. Moreover, it should be performed by a low-privilege user whenever possible, to prevent extraction of files that could compro…
  5. No fix planned, says the vendor Red Hat Product Security CVE-2019-14866 · 2 productsOut of support scope

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.17.3read 2026-10-23
  • CNACVSS 3.06.7known since 2026-10-23
  • NVDCVSS 2.06.9read 2026-10-23
  • CNAweakness (CWE)CWE-20known since 2026-10-23
  • FIRST EPSSEPSS score0.7 %2026-11-03
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Published
2020-01-07
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-g3pr-277r-xcx7

Frequently asked questions

What is CVE-2019-14866?

In all versions of cpio before 2.13 does not properly validate input files when generating TAR archives. When cpio is used to create TAR archives from paths an attacker can write to, the resulting archive may contain files with permissions the attacker did not have or in paths he did not have access to. Extracting those archives from a high-privilege user without carefully reviewing them may lead to the compromise of the system.

Is CVE-2019-14866 actively exploited?

Active exploitation of CVE-2019-14866 has not been confirmed. Its EPSS score was 0.7% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-14866?

CVE-2019-14866 has a CVSS v3 base score of 7.3 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

Running cpio? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record