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 | |
|---|---|---|---|---|---|
| red_hat_products Red Hat · All currently supported Red Hat products | not affected vulnerable code not present | no version stated | not applicable | csaf_redhat | |
| Google/Chrome Google · Chrome | affected | >= 116.0.5845.179, < 116.0.5845.179 | none available | cve_cna | |
| google/chrome google · chrome | affected | * | none available | cve_adp | |
| debian/debian_linux debian · debian_linux | affected | 11.0 | none available | cve_adp | |
| debian/debian_linux debian · debian_linux | affected | 12.0 | none available | cve_adp | |
| fedoraproject/fedora fedoraproject · fedora | affected | 37 | none available | cve_adp | |
| fedoraproject/fedora fedoraproject · fedora | affected | 38 | none available | cve_adp | |
| fedoraproject/fedora fedoraproject · fedora | affected | 39 | 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.