Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| https://github.com/livewire/livewire | affected | >= ea97977ac080fff70f0a35280bdb7322c246345e, < ef04be759da41b14d2d129e670533180a44987dc | vendor fix → ef04be759da41b14d2d129e670533180a44987dc | osv | |
| livewire/livewire | affected | >= 3.0.0-beta.1, < 3.6.4 | vendor fix → 3.6.4 | osv GHSA-29cq-5w36-x7w3 | |
| https://github.com/livewire/livewire | fixed | ef04be759da41b14d2d129e670533180a44987dc | vendor fix → ef04be759da41b14d2d129e670533180a44987dc | osv | |
| livewire/livewire | fixed | 3.6.4 | vendor fix → 3.6.4 | osv GHSA-29cq-5w36-x7w3 | |
| livewire/livewire livewire · livewire | affected | >= 3.0.0-beta.1, < 3.6.4 | none available | cve_cna |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.