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/laravel/framework | affected | <= d724ce0aa61bbd9adf658215eec484f5dd6711d6 | none available | osv | |
| https://github.com/laravel/framework | affected | >= 56a58e0fa3d845bb992d7c64ac9bb6d0c24b745a, <= acc6b5c54ab196d3358f60acc5f55d9ebaaccc02 | none available | osv | |
| laravel/framework | affected | <= 5.5.40 | none available | osv GHSA-qvqm-h22r-4cp9 | |
| laravel/framework | affected | >= 5.6.0, < 5.6.30 | vendor fix → 5.6.30 | osv GHSA-qvqm-h22r-4cp9 | |
| laravel/framework | fixed | 5.6.30 | vendor fix → 5.6.30 | osv GHSA-qvqm-h22r-4cp9 | |
| n/a/n/a n/a · n/a | affected | no version stated vendor label: all versions | 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.