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 | |
|---|---|---|---|---|---|
| apache-superset | affected | < 2.1.0 | vendor fix → 2.1.0 | osv GHSA-5cx2-vq3h-x52c | |
| https://github.com/apache/superset | affected | <= 507a7562e099707ab1103f4173d6c3b0ade2ec2d | none available | osv | |
| superset | affected | < 2.0.2 | vendor fix → 2.0.2 | osv BIT-superset-2023-27524 | |
| apache-superset | fixed | 2.1.0 | vendor fix → 2.1.0 | osv GHSA-5cx2-vq3h-x52c | |
| superset | fixed | 2.0.2 | vendor fix → 2.0.2 | osv BIT-superset-2023-27524 | |
| Apache Software Foundation/Apache Superset Apache Software Foundation · Apache Superset | affected | <= 2.0.1 | 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.