Vulnerability Database · Packagist · Package report

zendframework/zendframework: vulnerability history, versions and safety

zendframework/zendframework is a package in the Packagist ecosystem. Vulert records 20 vulnerabilities for it across 75 releases, from Jun 2021 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
20 vulnerabilities recorded C5 H6 M9
i
1 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 zendframework/zendframework i

Updated on 23 Oct 2026

Careful: one of the 20 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 20 over 2 years · 0 in the last year i
  • Latest disclosure 07 Jun 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 1 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 zendframework/zendframework, 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
3.0.0 C1 No Details →
2.5.3 C1 No Details →
2.5.2 C1 No Details →
2.5.1 C1 H1 No Details →
2.5.0 C1 H1 No Details →
2.4.13 C1 M1 No Details →
2.4.12 C1 M1 No Details →
2.4.11 C1 M1 No Details →
2.4.10 C1 M2 No Details →
2.4.9 C1 M2 No Details →
2.4.8 C1 M3 No Details →
2.4.7 C1 M3 No Details →
2.4.6 C1 M3 No Details →
2.4.5 C1 M4 No Details →
2.4.4 C1 M4 No Details →
2.4.3 C1 M4 No Details →
2.4.2 C1 M4 No Details →
2.4.1 C1 M4 No Details →
2.4.0 C1 M4 No Details →
2.4.0rc7 C1 M4 No Details →
2.4.0rc6 C1 M4 No Details →
2.4.0rc5 C1 M4 No Details →
2.4.0rc4 C1 M4 No Details →
2.4.0rc3 C1 M4 No Details →
2.4.0rc2 C1 M4 No Details →
2.4.0rc1 C1 M4 No Details →
2.3.9 C1 M4 No Details →
2.3.8 C1 M4 No Details →
2.3.7 C1 M4 No Details →
2.3.6 C1 M4 No Details →
2.3.5 C1 H1 M4 No Details →
2.3.4 C1 H1 M4 No Details →
2.3.3 C1 H1 M4 No Details →
2.3.2 C1 H1 M4 No Details →
2.3.1 C1 H1 M4 No Details →
2.3.0 C1 H1 M4 No Details →
2.2.10 C1 M4 No Details →
2.2.9 C2 M4 No Details →
2.2.8 C2 M5 No Details →
2.2.7 C2 M5 No Details →
2.2.6 C2 M6 No Details →
2.2.5 C2 M6 No Details →
2.2.4 C2 H1 M6 No Details →
2.2.3 C2 H1 M6 No Details →
2.2.2 C2 H1 M6 No Details →
2.2.1 C2 H1 M6 No Details →
2.2.0 C2 H1 M6 No Details →
2.2.0rc3 C2 M6 No Details →
2.2.0rc2 C2 M6 No Details →
2.2.0rc1 C2 M6 No Details →
2.1.6 C2 M6 No Details →
2.1.5 C3 M6 No Details →
2.1.4 C3 M6 No Details →
2.1.3 C3 M6 No Details →
2.1.2 C3 M6 No Details →
2.1.1 C3 M6 No Details →
2.1.0 C3 M6 No Details →
2.0.8 C2 M7 No Details →
2.0.7 C2 H3 M7 No Details →
2.0.6 C2 H3 M7 No Details →
2.0.5 C2 H3 M7 No Details →
2.0.4 C2 H3 M8 No Details →
2.0.3 C2 H3 M8 No Details →
2.0.2 C2 H3 M8 No Details →
2.0.1 C2 H3 M8 No Details →
2.0.0 C2 H3 M9 No Details →
2.0.0rc7 C2 M1 No Details →
2.0.0rc6 C2 M1 No Details →
2.0.0rc5 C2 M1 No Details →
2.0.0rc4 C2 M1 No Details →
2.0.0rc3 C2 M1 No Details →
2.0.0rc2 C2 M1 No Details →
2.0.0rc1 C2 M1 No Details →
2.0.0beta5 C2 M1 No Details →
2.0.0beta4 C2 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 7
  • 2024 12

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

03 Vulnerabilities

Recorded vulnerabilities for zendframework/zendframework

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 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 zendframework/zendframework

Is zendframework/zendframework safe to use?

Vulert records 20 vulnerabilities for zendframework/zendframework in Packagist: 5 critical, 6 high, 9 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does zendframework/zendframework have?

20 vulnerabilities are recorded for zendframework/zendframework in the Packagist ecosystem: 5 critical, 6 high, 9 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 zendframework/zendframework vulnerabilities disclosed?

0 vulnerabilities were recorded for zendframework/zendframework in the last 12 months, and the oldest entry in this database dates to 08 Jun 2021. 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 zendframework/zendframework 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 zendframework/zendframework for upcoming vulnerabilities?

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