Vulnerability Database · Packagist · Package report

typo3/cms-workspaces: vulnerability history, versions and safety

typo3/cms-workspaces is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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-workspaces i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, none 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 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Sep 2025 i
  • Highest CVSS 7.1 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 typo3/cms-workspaces, 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
v12.4.36 H1 M1 Yes Details →
v12.4.35 H1 M1 Yes Details →
v12.4.34 H1 M1 Yes Details →
v12.4.33 H1 M1 Yes Details →
v12.4.32 H1 M1 Yes Details →
v12.4.31 H1 M1 Yes Details →
v12.4.30 H1 M1 Yes Details →
v12.4.29 H1 M1 Yes Details →
v12.4.28 H1 M1 Yes Details →
v12.4.27 H1 M1 Yes Details →
v12.4.26 H1 M1 Yes Details →
v12.4.25 H1 M1 Yes Details →
v12.4.24 H1 M1 Yes Details →
v12.4.23 H1 M1 Yes Details →
v12.4.22 H1 M1 Yes Details →
v12.4.21 H1 M1 Yes Details →
v12.4.20 H1 M1 Yes Details →
v12.4.19 H1 M1 Yes Details →
v12.4.18 H1 M1 Yes Details →
v12.4.17 H1 M1 Yes Details →
v12.4.16 H1 M1 Yes Details →
v12.4.15 H1 M1 Yes Details →
v12.4.14 H1 M1 Yes Details →
v12.4.13 H1 M1 Yes Details →
v12.4.12 H1 M1 Yes Details →
v12.4.11 H1 M1 Yes Details →
v12.4.10 H1 M1 Yes Details →
v12.4.9 H1 M1 Yes Details →
v12.4.8 H1 M1 Yes Details →
v12.4.7 H1 M1 Yes Details →
v12.4.6 H1 M1 Yes Details →
v12.4.5 H1 M1 Yes Details →
v12.4.4 H1 M1 Yes Details →
v12.4.3 H1 M1 Yes Details →
v12.4.2 H1 M1 Yes Details →
v12.4.1 H1 M1 Yes Details →
v12.4.0 H1 M1 Yes Details →
v12.3.0 H1 M1 Yes Details →
v12.2.0 H1 M1 Yes Details →
v12.1.3 H1 M1 Yes Details →
v12.1.2 H1 M1 Yes Details →
v12.1.1 H1 M1 Yes Details →
v12.1.0 H1 M1 Yes Details →
v12.0.0 H1 M1 Yes Details →
v11.5.41 H1 M1 Yes Details →
v11.5.40 H1 M1 Yes Details →
v11.5.39 H1 M1 Yes Details →
v11.5.38 H1 M1 Yes Details →
v11.5.37 H1 M1 Yes Details →
v11.5.36 H1 M1 Yes Details →
v11.5.35 H1 M1 Yes Details →
v11.5.34 H1 M1 Yes Details →
v11.5.33 H1 M1 Yes Details →
v11.5.32 H1 M1 Yes Details →
v11.5.31 H1 M1 Yes Details →
v11.5.30 H1 M1 Yes Details →
v11.5.29 H1 M1 Yes Details →
v11.5.28 H1 M1 Yes Details →
v11.5.27 H1 M1 Yes Details →
v11.5.26 H1 M1 Yes Details →
v11.5.25 H1 M1 Yes Details →
v11.5.24 H1 M1 Yes Details →
v11.5.23 H1 M1 Yes Details →
v11.5.22 H1 M1 Yes Details →
v11.5.21 H1 M1 Yes Details →
v11.5.20 H1 M1 Yes Details →
v11.5.19 H1 M1 Yes Details →
v11.5.18 H1 M1 Yes Details →
v11.5.17 H1 M1 Yes Details →
v11.5.16 H1 M1 Yes Details →
v11.5.15 H1 M1 Yes Details →
v11.5.14 H1 M1 Yes Details →
v11.5.13 H1 M1 Yes Details →
v11.5.12 H1 M1 Yes Details →
v11.5.11 H1 M1 Yes Details →
v11.5.10 H1 M1 Yes Details →
v11.5.9 H1 M1 Yes Details →
v11.5.8 H1 M1 Yes Details →
v11.5.7 H1 M1 Yes Details →
v11.5.6 H1 M1 Yes Details →
v11.5.5 H1 M1 Yes Details →
v11.5.4 H1 M1 Yes Details →
v11.5.3 H1 M1 Yes Details →
v11.5.2 H1 M1 Yes Details →
v11.5.1 H1 M1 Yes Details →
v11.5.0 H1 M1 Yes Details →
v11.4.0 H1 M1 Yes Details →
v11.3.3 H1 M1 Yes Details →
v11.3.2 H1 M1 Yes Details →
v11.3.1 H1 M1 Yes Details →
v11.3.0 H1 M1 Yes Details →
v11.2.0 H1 M1 Yes Details →
v11.1.1 H1 M1 Yes Details →
v11.1.0 H1 M1 Yes Details →
v11.0.0 H1 M1 Yes Details →
v10.4.37 H1 M1 Yes Details →
v10.4.36 H1 M1 Yes Details →
v10.4.34 H1 M1 Yes Details →
v10.4.33 H1 M1 Yes Details →
v10.4.32 H1 M1 Yes Details →
v10.4.31 H1 M1 Yes Details →
v10.4.30 H1 M1 Yes Details →
v10.4.29 H1 M1 Yes Details →
v10.4.28 H1 M1 Yes Details →
v10.4.27 H1 M1 Yes Details →
v10.4.26 H1 M1 Yes Details →
v10.4.25 H1 M1 Yes Details →
v10.4.24 H1 M1 Yes Details →
v10.4.23 H1 M1 Yes Details →
v10.4.22 H1 M1 Yes Details →
v10.4.21 H1 M1 Yes Details →
v10.4.20 H1 M1 Yes Details →
v10.4.19 H1 M1 Yes Details →
v10.4.18 H1 M1 Yes Details →
v10.4.17 H1 M1 Yes Details →
v10.4.16 H1 M1 Yes Details →
v10.4.15 H1 M1 Yes Details →
v10.4.14 H1 M1 Yes Details →
v10.4.13 H1 M1 Yes Details →
v10.4.12 H1 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for typo3/cms-workspaces

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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-workspaces

Is typo3/cms-workspaces safe to use?

Vulert records 2 vulnerabilities for typo3/cms-workspaces in Packagist: 0 critical, 1 high, 1 medium and 0 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 typo3/cms-workspaces have?

2 vulnerabilities are recorded for typo3/cms-workspaces in the Packagist ecosystem: 0 critical, 1 high, 1 medium and 0 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-workspaces vulnerabilities disclosed?

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

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