CVE-2020-37239
libbabl 0.1.62 double-free detection bypass enables memory corruption.
Is CVE-2020-37239 being exploited?
Not confirmed. CVE-2020-37239 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2020-37239?
CVE-2020-37239 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2020-37239?
Not known from our data. No patch reference has been recorded for CVE-2020-37239, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2020-37239 affect?
CVE-2020-37239 affects libbabl 0.1.62. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2020-37239?
Upgrade to fixed libbabl version when released; monitor advisories.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory corruption via double free of freed chunks; could lead to code execution in apps using libbabl.
Patch when possible
- affected0.1.62
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.