Vulnerability Database · Packagist · Package report

filament/infolists: vulnerability history, versions and safety

filament/infolists is a package in the Packagist ecosystem. Vulert records 1 vulnerability for it across 73 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 23 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on filament/infolists i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 1 vulnerability on record across 1 year, 1 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 1 over 1 year · 1 in the last year i
  • Latest disclosure 23 Jun 2026 i
  • Highest CVSS 6.4 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 filament/infolists, 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
v4.11.4 M1 Yes Details →
v4.11.3 M1 Yes Details →
v4.11.2 M1 Yes Details →
v4.11.1 M1 Yes Details →
v4.11.0 M1 Yes Details →
v4.10.2 M1 Yes Details →
v4.10.1 M1 Yes Details →
v4.10.0 M1 Yes Details →
v4.9.5 M1 Yes Details →
v4.9.4 M1 Yes Details →
v4.9.3 M1 Yes Details →
v4.9.2 M1 Yes Details →
v4.9.1 M1 Yes Details →
v4.9.0 M1 Yes Details →
v4.8.5 M1 Yes Details →
v4.8.4 M1 Yes Details →
v4.8.3 M1 Yes Details →
v4.8.2 M1 Yes Details →
v4.8.1 M1 Yes Details →
v4.8.0 M1 Yes Details →
v4.7.4 M1 Yes Details →
v4.7.3 M1 Yes Details →
v4.7.2 M1 Yes Details →
v4.7.1 M1 Yes Details →
v4.7.0 M1 Yes Details →
v4.6.3 M1 Yes Details →
v4.6.2 M1 Yes Details →
v4.6.1 M1 Yes Details →
v4.6.0 M1 Yes Details →
v4.5.3 M1 Yes Details →
v4.5.2 M1 Yes Details →
v4.5.1 M1 Yes Details →
v4.5.0 M1 Yes Details →
v4.4.0 M1 Yes Details →
v4.3.1 M1 Yes Details →
v4.3.0 M1 Yes Details →
v4.2.4 M1 Yes Details →
v4.2.3 M1 Yes Details →
v4.2.2 M1 Yes Details →
v4.2.1 M1 Yes Details →
v4.2.0 M1 Yes Details →
v4.1.10 M1 Yes Details →
v4.1.9 M1 Yes Details →
v4.1.8 M1 Yes Details →
v4.1.7 M1 Yes Details →
v4.1.6 M1 Yes Details →
v4.1.5 M1 Yes Details →
v4.1.4 M1 Yes Details →
v4.1.3 M1 Yes Details →
v4.1.2 M1 Yes Details →
v4.1.1 M1 Yes Details →
v4.1.0 M1 Yes Details →
v4.0.20 M1 Yes Details →
v4.0.19 M1 Yes Details →
v4.0.18 M1 Yes Details →
v4.0.17 M1 Yes Details →
v4.0.16 M1 Yes Details →
v4.0.15 M1 Yes Details →
v4.0.14 M1 Yes Details →
v4.0.13 M1 Yes Details →
v4.0.12 M1 Yes Details →
v4.0.11 M1 Yes Details →
v4.0.10 M1 Yes Details →
v4.0.9 M1 Yes Details →
v4.0.8 M1 Yes Details →
v4.0.7 M1 Yes Details →
v4.0.6 M1 Yes Details →
v4.0.5 M1 Yes Details →
v4.0.4 M1 Yes Details →
v4.0.3 M1 Yes Details →
v4.0.2 M1 Yes Details →
v4.0.1 M1 Yes Details →
v4.0.0 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for filament/infolists

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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 filament/infolists

Is filament/infolists safe to use?

Vulert records 1 vulnerabilities for filament/infolists in Packagist: 0 critical, 0 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 filament/infolists have?

1 vulnerability is recorded for filament/infolists in the Packagist ecosystem: 0 critical, 0 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 filament/infolists vulnerabilities disclosed?

1 vulnerability was recorded for filament/infolists in the last 12 months, and the oldest entry in this database dates to 23 Jun 2026. 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 filament/infolists 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 filament/infolists for upcoming vulnerabilities?

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