How severe is CVE-2020-16269?

CVE-2020-16269 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2020-16269 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-16269?

CVE-2020-16269 primarily affects Radare Radare2. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-16269?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-16269 published?

CVE-2020-16269 was published on 2020-08-03 and last updated on 2026-06-17.

CVE-2020-16269

CVE-2020-16269 is a medium-severity vulnerability in Radare Radare2 with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 4.3
EPSS exploit prediction: 1% (58th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Radare Radare2
Published: 2020-08-03
Last modified: 2026-06-17

Description

radare2 4.5.0 misparses DWARF information in executable files, causing a segmentation fault in parse_typedef in type_dwarf.c via a malformed DW_AT_name in the .debug_info section.

Frequently asked questions

What is CVE-2020-16269?: radare2 4.5.0 misparses DWARF information in executable files, causing a segmentation fault in parse_typedef in type_dwarf.c via a malformed DW_AT_name in the .debug_info section.
How severe is CVE-2020-16269?: CVE-2020-16269 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-16269 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (58th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-16269?: CVE-2020-16269 primarily affects Radare Radare2. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-16269?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-16269 published?: CVE-2020-16269 was published on 2020-08-03 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:radare:radare2:4.5.0:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*

More vulnerabilities in Radare Radare2

CVE-2021-32495 — Critical (CVSS 10.0): Radare2 has a use-after-free vulnerability in pyc parser's get_none_object function. Attacker can read freed memory…
CVE-2021-32494 — Critical (CVSS 10.0): Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. This allow attackers to create…
CVE-2025-1864 — Critical (CVSS 9.8): Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in radareorg radare2 allows…
CVE-2025-1744 — Critical (CVSS 9.8): Out-of-bounds Write vulnerability in radareorg radare2 allows heap-based buffer over-read or buffer overflow.This…
CVE-2024-29646 — Critical (CVSS 9.8): Buffer Overflow vulnerability in radarorg radare2 v.5.8.8 allows an attacker to execute arbitrary code via the name,…
CVE-2023-46570 — Critical (CVSS 9.8): An out-of-bounds read in radare2 v.5.8.9 and before exists in the print_insn32 function of…

All CVEs affecting Radare Radare2 →