CyberzSOC

Applicability
← Back to CVE-2020-11978

CVE-2020-11978

CVSS 8.8 In CISA KEV Apache

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.

Does it affect your version?

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.

What each source says

OSV.dev (incl. GHSA)
precedence 80 · revised 2026-09-08
4 affected 4 fixed
CVE List v5 (CNA container)
precedence 60 · revised 2025-10-21
1 affected

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.

Statements (7)

Product Status Versions Remediation Source
airflow affected < 1.10.11 vendor fix → 1.10.11 osv BIT-airflow-2020-11978
apache-airflow affected < 1.10.11rc1 vendor fix → 1.10.11rc1 osv GHSA-rvmq-4x66-q7j3
https://github.com/apache/airflow affected < f53b1d0041d3dc087ff2c6addaa72266e784b928 vendor fix → f53b1d0041d3dc087ff2c6addaa72266e784b928 osv
airflow fixed 1.10.11 vendor fix → 1.10.11 osv BIT-airflow-2020-11978
apache-airflow fixed 1.10.11rc1 vendor fix → 1.10.11rc1 osv GHSA-rvmq-4x66-q7j3
https://github.com/apache/airflow fixed f53b1d0041d3dc087ff2c6addaa72266e784b928 vendor fix → f53b1d0041d3dc087ff2c6addaa72266e784b928 osv
Apache Software Foundation/Apache Airflow Apache Software Foundation · Apache Airflow affected 1.10.10 and below 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.