VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libdwarf: vulnerability history, versions and safety

libdwarf is a package in the OSS-Fuzz ecosystem. Vulert records 14 vulnerabilities for it across 14 releases, from May 2022 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded H6 M6 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 21 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libdwarf vulnerabilities

Vulert verdict on libdwarf i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 21 May 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 14 vulnerabilities on record across 4 years, 3 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 14 over 4 years · 3 in the last year i
  • Latest disclosure 21 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libdwarf, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 14 of 14 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 9
  • 2025 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libdwarf

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-use-after-free Vulnerability in libdwarf: Critical Memory Management Flaw N/A high eab3c42416fb5c14c1f5ba60294642ca34599b11 15 Jan 2026
Heap-buffer-overflow in libdwarf: _dwarf_memcpy_noswap_bytes N/A medium aea77dad8745d9aad5275c3226e4e3156effa71f 04 Oct 2023
Heap-buffer-overflow in libdwarf: _dwarf_memcpy_noswap_bytes N/A medium 3a658bd1dd7437948cecbf82bb9b24f5f6122a7d 07 Oct 2023
Heap Buffer Overflow Vulnerability in libdwarf Package N/A medium aedc3c4cebdc84fe1e4b342df18b1b53110df534 09 Aug 2025
Heap-buffer-overflow in libdwarf: _dwarf_memcpy_swap_bytes N/A medium e8df98c5c6629b75402b8ea5e5a44797fb3ae4b3 01 Oct 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libdwarf

Is libdwarf safe to use?

Vulert records 14 vulnerabilities for libdwarf in OSS-Fuzz: 0 critical, 6 high, 6 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does libdwarf have?

14 vulnerabilities are recorded for libdwarf in the OSS-Fuzz ecosystem: 0 critical, 6 high, 6 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libdwarf vulnerabilities disclosed?

3 vulnerabilities were recorded for libdwarf in the last 12 months, and the oldest entry in this database dates to 01 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libdwarf are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libdwarf for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libdwarf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.