Vulnerability Database · Packagist · Package report

contao/core-bundle: vulnerability history, versions and safety

contao/core-bundle is a package in the Packagist ecosystem. Vulert records 30 vulnerabilities for it across 120 releases, from Dec 2019 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
30 vulnerabilities recorded H5 M22 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 09 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on contao/core-bundle i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 09 Oct 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 30 vulnerabilities on record across 6 years, 8 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 30 over 6 years · 8 in the last year i
  • Latest disclosure 09 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for contao/core-bundle, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.7.11 M2 Yes Details →
5.7.10 M2 Yes Details →
5.7.9 M2 Yes Details →
5.7.8 M2 Yes Details →
5.7.7 M2 Yes Details →
5.7.6 M2 Yes Details →
5.7.5 M2 Yes Details →
5.7.4 M2 Yes Details →
5.7.3 M2 Yes Details →
5.7.2 M2 Yes Details →
5.7.1 M2 Yes Details →
5.7.0 M1 Yes Details →
5.3.49 M3 L1 Yes Details →
5.3.48 M3 L1 Yes Details →
5.3.47 M3 L1 Yes Details →
5.3.46 M3 L1 Yes Details →
5.3.45 M3 L1 Yes Details →
5.3.44 M3 L1 Yes Details →
5.3.43 M3 L1 Yes Details →
5.3.42 M3 L1 Yes Details →
5.3.41 M3 L1 Yes Details →
5.3.40 M3 L1 Yes Details →
5.3.39 M3 L1 Yes Details →
5.3.38 M3 L1 Yes Details →
5.3.37 M6 L1 Yes Details →
5.3.36 M6 L1 Yes Details →
5.3.35 M6 L1 Yes Details →
5.3.34 M6 L1 Yes Details →
5.3.33 M6 L1 Yes Details →
5.3.32 M6 L1 Yes Details →
5.3.31 M6 L1 Yes Details →
5.3.30 M6 L1 Yes Details →
5.3.29 M6 L1 Yes Details →
5.3.28 M6 L1 Yes Details →
5.3.27 M6 L1 Yes Details →
5.3.26 M6 L1 Yes Details →
5.3.25 M6 L1 Yes Details →
5.3.24 M6 L1 Yes Details →
5.3.23 M6 L1 Yes Details →
5.3.22 M6 L1 Yes Details →
5.3.21 M6 L1 Yes Details →
5.3.20 M6 L1 Yes Details →
5.3.19 M6 L1 Yes Details →
5.3.18 M6 L1 Yes Details →
5.3.17 M6 L1 Yes Details →
5.3.16 M6 L1 Yes Details →
5.3.15 M6 L1 Yes Details →
5.3.14 M6 L1 Yes Details →
5.3.13 M6 L1 Yes Details →
5.3.12 M6 L1 Yes Details →
5.3.11 M6 L1 Yes Details →
5.3.10 M6 L1 Yes Details →
5.3.9 M6 L1 Yes Details →
5.3.8 M6 L1 Yes Details →
5.3.7 M6 L1 Yes Details →
5.3.6 M6 L1 Yes Details →
5.3.5 M6 L1 Yes Details →
5.3.4 M6 L1 Yes Details →
5.3.3 M6 L1 Yes Details →
5.3.2 M6 L1 Yes Details →
5.3.1 M6 L1 Yes Details →
5.3.0 M6 L1 Yes Details →
5.3.0-RC4 M5 L1 Yes Details →
5.3.0-RC3 M5 L1 Yes Details →
5.3.0-RC2 M5 L1 Yes Details →
5.3.0-RC1 M5 L1 Yes Details →
5.2.10 M5 L1 Yes Details →
5.2.9 M5 L1 Yes Details →
5.2.8 M5 L1 Yes Details →
5.2.7 M5 L1 Yes Details →
5.2.6 M5 L1 Yes Details →
5.2.5 M5 L1 Yes Details →
5.2.4 M5 L1 Yes Details →
5.2.3 M5 L1 Yes Details →
5.2.2 M5 L1 Yes Details →
5.2.1 M5 L1 Yes Details →
5.2.0 M5 L1 Yes Details →
5.2.0-RC6 M5 L1 Yes Details →
5.2.0-RC5 M5 L1 Yes Details →
5.2.0-RC4 M5 L1 Yes Details →
5.2.0-RC3 M5 L1 Yes Details →
5.2.0-RC2 M5 L1 Yes Details →
5.2.0-RC1 M5 L1 Yes Details →
5.1.11 M5 L1 Yes Details →
5.1.10 M5 L1 Yes Details →
5.1.9 M5 L1 Yes Details →
5.1.8 M5 L1 Yes Details →
5.1.7 M5 L1 Yes Details →
5.1.6 M5 L1 Yes Details →
5.1.5 M5 L1 Yes Details →
5.1.4 M5 L1 Yes Details →
5.1.3 M5 L1 Yes Details →
5.1.2 M5 L1 Yes Details →
5.1.1 M5 L1 Yes Details →
5.1.0 M5 L1 Yes Details →
5.1.0-RC3 M5 L1 Yes Details →
5.1.0-RC2 M5 L1 Yes Details →
5.1.0-RC1 M5 L1 Yes Details →
5.0.10 M5 L1 Yes Details →
5.0.9 M5 L1 Yes Details →
5.0.8 M5 L1 Yes Details →
5.0.7 M5 L1 Yes Details →
5.0.6 M5 L1 Yes Details →
5.0.5 M5 L1 Yes Details →
5.0.4 M5 L1 Yes Details →
5.0.3 M5 L1 Yes Details →
5.0.2 M5 L1 Yes Details →
5.0.1 M5 L1 Yes Details →
5.0.0 M5 L1 Yes Details →
5.0.0-RC4 M4 L1 Yes Details →
5.0.0-RC3 M4 L1 Yes Details →
5.0.0-RC2 M4 L1 Yes Details →
5.0.0-RC1 M4 L1 Yes Details →
4.13.58 M3 L1 Yes Details →
4.13.57 M3 L1 Yes Details →
4.13.56 M4 L2 Yes Details →
4.13.55 M5 L2 Yes Details →
4.13.54 M5 L2 Yes Details →
4.13.53 M6 L2 Yes Details →
4.13.52 M6 L2 Yes Details →

Newest 120 of 411 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2020 1
  • 2021 4
  • 2022 1
  • 2023 1
  • 2024 7
  • 2025 7
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 8 of the 30 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About contao/core-bundle

Is contao/core-bundle safe to use?

Vulert records 30 vulnerabilities for contao/core-bundle in Packagist: 0 critical, 5 high, 22 medium and 3 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does contao/core-bundle have?

30 vulnerabilities are recorded for contao/core-bundle in the Packagist ecosystem: 0 critical, 5 high, 22 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new contao/core-bundle vulnerabilities disclosed?

8 vulnerabilities were recorded for contao/core-bundle in the last 12 months, and the oldest entry in this database dates to 17 Dec 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of contao/core-bundle are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor contao/core-bundle for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the contao/core-bundle version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.