Vulnerability Database · Packagist · Package report

typo3/cms: vulnerability history, versions and safety

typo3/cms is a package in the Packagist ecosystem. Vulert records 134 vulnerabilities for it across 120 releases, from Apr 2022 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
134 vulnerabilities recorded C6 H25 M92 L11
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on typo3/cms i

Updated on 23 Oct 2026

Careful: 5 of the 134 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 134 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 134 over 2 years · 0 in the last year i
  • Latest disclosure 07 Jun 2024 i
  • Highest CVSS 9.9 i
  • With no published fix 5 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 typo3/cms, 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
8.7.2 H5 M12 No Details →
8.7.1 H5 M12 No Details →
8.7.0 H5 M12 No Details →
8.6.1 H5 M12 No Details →
8.6.0 H5 M13 No Details →
8.5.1 H5 M13 No Details →
8.5.0 H5 M13 No Details →
8.4.1 H3 M13 No Details →
8.4.0 H3 M13 No Details →
8.3.1 H3 M13 No Details →
8.3.0 H3 M13 No Details →
8.2.1 H3 M13 No Details →
8.2.0 H3 M13 No Details →
8.1.2 H3 M12 No Details →
8.1.1 H3 M12 No Details →
8.1.0 H3 M12 No Details →
8.0.1 H3 M12 No Details →
8.0.0 H3 M12 No Details →
7.6.19 C1 H4 M9 L1 No Details →
7.6.18 C1 H4 M9 L1 No Details →
7.6.17 C1 H4 M9 L1 No Details →
7.6.16 C1 H4 M9 L1 No Details →
7.6.15 C1 H4 M11 L1 No Details →
7.6.14 C1 H4 M10 L1 No Details →
7.6.13 C1 H4 M10 L1 No Details →
7.6.12 C1 H4 M10 L1 No Details →
7.6.11 C1 H4 M10 L1 No Details →
7.6.10 C1 H4 M10 L1 No Details →
7.6.9 C1 H4 M11 L1 No Details →
7.6.8 C1 H4 M11 L1 No Details →
7.6.7 C1 H4 M11 L1 No Details →
7.6.6 C1 H4 M11 L1 No Details →
7.6.5 C1 H4 M11 L1 No Details →
7.6.4 C1 H4 M11 L1 No Details →
7.6.3 C1 H4 M11 L1 No Details →
7.6.2 C1 H4 M11 L1 No Details →
7.6.1 C1 H4 M11 L1 No Details →
7.6.0 C1 H4 M11 L1 No Details →
7.5.0 H3 M8 No Details →
7.4.0 H3 M8 No Details →
7.3.1 H3 M8 No Details →
7.3.0 H3 M8 No Details →
7.2.0 H3 M8 No Details →
7.1.0 H3 M9 No Details →
7.0.2 H3 M9 No Details →
7.0.1 H3 M9 No Details →
7.0.0 H3 M9 No Details →
6.2.31 M2 No Details →
6.2.30 M2 No Details →
6.2.29 H1 M2 No Details →
6.2.28 H1 M4 No Details →
6.2.27 H1 M4 No Details →
6.2.26 H1 M6 No Details →
6.2.25 H1 M11 No Details →
6.2.24 C1 H1 M11 No Details →
6.2.23 C1 H1 M11 No Details →
6.2.22 C1 H1 M11 No Details →
6.2.21 C1 H1 M11 No Details →
6.2.20 C1 H1 M11 No Details →
6.2.19 C1 H1 M15 No Details →
6.2.18 C1 H2 M19 No Details →
6.2.17 C1 H3 M22 No Details →
6.2.16 C1 H3 M22 No Details →
6.2.15 C1 H3 M31 No Details →
6.2.14 C1 H3 M32 L1 No Details →
6.2.13 C1 H5 M35 L1 No Details →
6.2.12 C1 H5 M35 L1 No Details →
6.2.11 C1 H5 M35 L1 No Details →
6.2.10 C1 H5 M35 L1 No Details →
6.2.10-rc1 C1 H5 M35 L1 No Details →
6.2.9 C1 H5 M35 L1 No Details →
6.2.8 C1 H6 M35 L1 No Details →
6.2.7 C1 H6 M35 L1 No Details →
6.2.6 C1 H6 M35 L1 No Details →
6.2.5 C1 H7 M35 L1 No Details →
6.2.4 C1 H7 M35 L1 No Details →
6.2.3 C1 H7 M35 L1 No Details →
6.2.2 C1 H7 M38 L1 No Details →
6.2.1 C1 H7 M38 L1 No Details →
6.2.0 C1 H7 M38 L1 No Details →
v14.2.0 M1 No Details →
v14.1.1 M1 No Details →
v14.1.0 M1 No Details →
v14.0.2 M1 No Details →
v14.0.1 M1 No Details →
v14.0.0 M1 No Details →
v13.4.27 M1 No Details →
v13.4.26 M1 No Details →
v13.4.25 M1 No Details →
v13.4.24 M1 No Details →
v13.4.23 M1 No Details →
v13.4.22 M1 No Details →
v13.4.21 M1 No Details →
v13.4.20 M1 No Details →
v13.4.19 M1 No Details →
v13.4.18 M1 No Details →
v13.4.17 M1 No Details →
v13.4.16 M1 No Details →
v13.4.15 M1 No Details →
v13.4.14 M1 No Details →
v13.4.13 M1 No Details →
v13.4.12 M1 No Details →
v13.4.11 M1 No Details →
v13.4.10 M1 No Details →
v13.4.9 M1 No Details →
v13.4.8 M1 No Details →
v13.4.7 M1 No Details →
v13.4.6 M1 No Details →
v13.4.5 M1 No Details →
v13.4.4 M1 No Details →
v13.4.3 M1 No Details →
v13.4.2 M1 No Details →
v13.4.1 M1 No Details →
v13.4.0 M1 No Details →
v13.3.1 M1 No Details →
v13.3.0 M1 No Details →
v13.2.1 M1 No Details →
v13.2.0 M1 No Details →
v13.1.1 M1 No Details →
v13.1.0 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 61
  • 2024 73

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

03 Vulnerabilities

Recorded vulnerabilities for typo3/cms

The 5 most severe of 134 vulnerabilities recorded for this package

Search all 134 in the database →

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 typo3/cms

Is typo3/cms safe to use?

Vulert records 134 vulnerabilities for typo3/cms in Packagist: 6 critical, 25 high, 92 medium and 11 low. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does typo3/cms have?

134 vulnerabilities are recorded for typo3/cms in the Packagist ecosystem: 6 critical, 25 high, 92 medium and 11 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new typo3/cms vulnerabilities disclosed?

0 vulnerabilities were recorded for typo3/cms in the last 12 months, and the oldest entry in this database dates to 22 Apr 2022. 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 typo3/cms 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 typo3/cms for upcoming vulnerabilities?

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