Vulnerability Database · Packagist · Package report

livewire/livewire: vulnerability history, versions and safety

livewire/livewire is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 98 releases, from Feb 2024 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 H2 M3
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 02 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on livewire/livewire i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 2 years, 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 6 over 2 years · 1 in the last year i
  • Latest disclosure 02 Sep 2026 i
  • Highest CVSS 9.2 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 livewire/livewire, 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
v3.8.2 M1 Yes Details →
v3.8.1 M1 Yes Details →
v3.8.0 M1 Yes Details →
v3.7.15 M1 Yes Details →
v3.7.14 M1 Yes Details →
v3.7.14-beta.1 M1 Yes Details →
v3.7.13 M1 Yes Details →
v3.7.12 M1 Yes Details →
v3.7.11 M1 Yes Details →
v3.7.10 M1 Yes Details →
v3.7.9 M1 Yes Details →
v3.7.8 M1 Yes Details →
v3.7.7 M1 Yes Details →
v3.7.6 M1 Yes Details →
v3.7.5 M1 Yes Details →
v3.7.4 M1 Yes Details →
v3.7.3 M1 Yes Details →
v3.7.2 M1 Yes Details →
v3.7.1 M1 Yes Details →
v3.7.0 M1 Yes Details →
v3.7.0-beta.2 M1 Yes Details →
v3.7.0-beta.1 M1 Yes Details →
v3.6.4 M1 Yes Details →
v3.6.3 C1 M1 Yes Details →
v3.6.2 C1 M1 Yes Details →
v3.6.1 C1 M1 Yes Details →
v3.6.0 C1 M1 Yes Details →
v3.5.20 C1 M1 Yes Details →
v3.5.19 C1 M1 Yes Details →
v3.5.18 C1 M1 Yes Details →
v3.5.17 C1 M1 Yes Details →
v3.5.16 C1 M1 Yes Details →
v3.5.15 C1 M1 Yes Details →
v3.5.14 C1 M1 Yes Details →
v3.5.13 C1 M1 Yes Details →
v3.5.12 C1 M1 Yes Details →
v3.5.11 C1 M1 Yes Details →
v3.5.10 C1 M1 Yes Details →
v3.5.9 C1 M1 Yes Details →
v3.5.8 C1 M1 Yes Details →
v3.5.7 C1 M1 Yes Details →
v3.5.6 C1 M1 Yes Details →
v3.5.5 C1 M1 Yes Details →
v3.5.4 C1 M1 Yes Details →
v3.5.3 C1 M1 Yes Details →
v3.5.2 C1 M1 Yes Details →
v3.5.1 C1 H1 M1 Yes Details →
v3.5.0 C1 H1 M1 Yes Details →
v3.4.12 C1 H1 M1 Yes Details →
v3.4.11 C1 H1 M1 Yes Details →
v3.4.10 C1 H1 M1 Yes Details →
v3.4.9 C1 H1 M1 Yes Details →
v3.4.8 C1 H1 M2 Yes Details →
v3.4.7 C1 H1 M2 Yes Details →
v3.4.6 C1 H1 M2 Yes Details →
v3.4.5 C1 H1 M2 Yes Details →
v3.4.4 C1 H1 M2 Yes Details →
v3.4.3 C1 H1 M2 Yes Details →
v3.4.2 C1 H1 M2 Yes Details →
v3.4.1 C1 H1 M2 Yes Details →
v3.4.0 C1 H1 M2 Yes Details →
v3.3.5 C1 H1 M2 Yes Details →
v3.3.4 C1 H1 M1 Yes Details →
v3.3.3 C1 H1 M1 Yes Details →
v3.3.2 C1 H1 M1 Yes Details →
v3.3.1 C1 H1 M1 Yes Details →
v3.3.0 C1 H1 M1 Yes Details →
v3.2.6 C1 H1 M1 Yes Details →
v3.2.5 C1 H1 M1 Yes Details →
v3.2.4 C1 H1 M1 Yes Details →
v3.2.3 C1 H1 M1 Yes Details →
v3.2.2 C1 H1 M1 Yes Details →
v3.2.1 C1 H1 M1 Yes Details →
v3.2.0 C1 H1 M1 Yes Details →
v3.1.0 C1 H1 M1 Yes Details →
v3.0.10 C1 H1 M1 Yes Details →
v3.0.9 C1 H1 M1 Yes Details →
v3.0.8 C1 H1 M1 Yes Details →
v3.0.7 C1 H1 M1 Yes Details →
v3.0.6 C1 H1 M1 Yes Details →
v3.0.5 C1 H1 M1 Yes Details →
v3.0.4 C1 H1 M1 Yes Details →
v3.0.3 C1 H2 M1 Yes Details →
v3.0.2 C1 H2 M1 Yes Details →
v3.0.1 C1 H2 M1 Yes Details →
v3.0.0 C1 H2 M1 Yes Details →
v3.0.0-beta.11 C1 H1 M1 Yes Details →
v3.0.0-beta.10 C1 H1 M1 Yes Details →
v3.0.0-beta.9 C1 H1 M1 Yes Details →
v3.0.0-beta.8 C1 H1 M1 Yes Details →
v3.0.0-beta.7 C1 H1 M1 Yes Details →
v3.0.0-beta.6 C1 H1 M1 Yes Details →
v3.0.0-beta.5 C1 H1 M1 Yes Details →
v3.0.0-beta.4 C1 H1 M1 Yes Details →
v3.0.0-beta.3 C1 H1 M1 Yes Details →
v3.0.0-beta.2 C1 H1 M1 Yes Details →
v3.0.0-beta.1 C1 H1 M1 Yes Details →
v2.2.5 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 4
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 6 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 livewire/livewire

Is livewire/livewire safe to use?

Vulert records 6 vulnerabilities for livewire/livewire in Packagist: 1 critical, 2 high, 3 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 livewire/livewire have?

6 vulnerabilities are recorded for livewire/livewire in the Packagist ecosystem: 1 critical, 2 high, 3 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 livewire/livewire vulnerabilities disclosed?

1 vulnerability was recorded for livewire/livewire in the last 12 months, and the oldest entry in this database dates to 01 Feb 2024. 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 livewire/livewire 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 livewire/livewire for upcoming vulnerabilities?

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