Skip to content
Fencer Vulns
high 8.0

CVE-2019-6338 json

third-party PEAR Archive_Tar library updates

published 2019-01-16 7 y ago modified 2026-09-19 50 d ago also DRUPAL-CORE-2019-001 , GHSA-6rmq-x2hv-vxpp , EUVD-2019-0782

cvss
8.0
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

In Drupal Core versions 7.x prior to 7.62, 8.6.x prior to 8.6.6 and 8.5.x prior to 8.5.9; Drupal core uses the third-party PEAR Archive_Tar library. This library has released a security update which impacts some Drupal configurations. Refer to CVE-2018-1000888 for details

Patch / fix

  • packagist drupal/drupal 7.62.0, 8.5.9, 8.6.6
  • packagist drupal/core 8.5.9, 8.6.6
  • Drupal Drupal core 7.62, 8.5.9, 8.6.6.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-6338 updated cvss 5.7

drupal: Vulnerability in the embedded PEAR Archive_Tar library

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.12% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P
GitHub 3.0 8.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist drupal/drupal
>=7.0.0, <7.62.0
>=8.0.0, <8.5.9
>=8.6.0, <8.6.6
7.62.0
8.5.9
8.6.6
packagist drupal/core
>=8.0.0, <8.5.9
>=8.6.0, <8.6.6
8.5.9
8.6.6

Affected products

  • Drupal Drupal core

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.