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/metabase/metabase | affected | >= 961caedc9983dfef7e25dfdfb0e18c9bde02dca4, <= 16d2e53436c3535e7040035bb23c4c3b2ddb9b79 | none available | osv | |
| https://github.com/metabase/metabase | affected | < 042a36e49574c749f944e19cf80360fd3dc322f0 | vendor fix → 042a36e49574c749f944e19cf80360fd3dc322f0 | osv | |
| https://github.com/metabase/metabase | fixed | 042a36e49574c749f944e19cf80360fd3dc322f0 | vendor fix → 042a36e49574c749f944e19cf80360fd3dc322f0 | osv | |
| metabase/metabase metabase · metabase | affected | < 0.40.5 | none available | cve_cna | |
| metabase/metabase metabase · metabase | affected | >= 1.0.0, < 1.40.5 | none available | cve_cna | |
| metabase/metabase metabase · metabase | affected | < 0.40.5 | none available | cve_adp | |
| metabase/metabase metabase · metabase | affected | >= 1.0.0, < 1.40.5 | none available | cve_adp |
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.