DRUPAL-CORE-2019-012 in drupal/core
Published 18 Dec 2019 · Updated 19 Sept 2026
Is your project on an affected drupal/core?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=8.0.0 <8.7.11 · >=8.8.0 <8.8.1
- Fixed in
- 8.7.11, 8.8.1
composer require drupal/core:^8.8.1Details
The Drupal project uses the third-party library Archive\_Tar, which has released a security improvement that is needed to protect some Drupal configurations.
Multiple vulnerabilities are possible if Drupal is configured to allow .tar, .tar.gz, .bz2 or .tlz file uploads and processes them.
The latest versions of Drupal update Archive_Tar to 1.4.9 to mitigate the file processing vulnerabilities.
*Edited to clarify the nature of the upstream release.*
Is DRUPAL-CORE-2019-012 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
More advisories for drupal/core
- LowCVE-2026-108514No summary published · 14 Oct 2026
- LowCVE-2026-108515No summary published · 14 Oct 2026
- LowCVE-2026-108097No summary published · 14 Oct 2026
- LowDRUPAL-CORE-2026-013No summary published · 16 Sept 2026
- LowCVE-2026-55805No summary published · 15 Jul 2026
- LowCVE-2026-15917No summary published · 15 Jul 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.