VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

binutils: vulnerability history, versions and safety

binutils is a package in the OSS-Fuzz ecosystem. Vulert records 24 vulnerabilities for it across 20 releases, from Oct 2021 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
24 vulnerabilities recorded H6 M12 U6
i
15 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 28 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all binutils vulnerabilities

Vulert verdict on binutils i

Updated on 23 Oct 2026

Careful: 15 of the 24 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 24 vulnerabilities on record across 4 years, 5 in the last year.

What to do: Plan around the 15 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 24 over 4 years · 5 in the last year i
  • Latest disclosure 28 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 15 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 binutils, 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 20 of 20 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 7
  • 2022 3
  • 2023 6
  • 2024 2
  • 2025 1
  • 2026 5

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

03 Vulnerabilities

Recorded vulnerabilities for binutils

The 5 most severe of 24 vulnerabilities recorded for this package

Search all 24 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in bfd_getl32 in binutils N/A medium 0bbd2b1ad0426aee86445cd7f0c86667624da7ca 21 May 2023
Global-buffer-overflow in fb_label_name in binutils N/A unrated No fix published 27 Oct 2021
Segv on unknown address in bfd_getl16 - binutils N/A unrated No fix published 09 Nov 2021
Global-buffer-overflow in xstrdup in binutils N/A unrated No fix published 12 Nov 2021
Index-Out-of-Bounds Vulnerability in Binutils: A Critical Flaw in print_insn_tic6x N/A medium 7e5ab72bd1d8fd5fa532bae67208e85ec4412230 28 Jun 2026

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 binutils

Is binutils safe to use?

Vulert records 24 vulnerabilities for binutils in OSS-Fuzz: 0 critical, 6 high, 12 medium and 0 low, plus 6 not yet rated. 15 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does binutils have?

24 vulnerabilities are recorded for binutils in the OSS-Fuzz ecosystem: 0 critical, 6 high, 12 medium and 0 low, plus 6 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 binutils vulnerabilities disclosed?

5 vulnerabilities were recorded for binutils in the last 12 months, and the oldest entry in this database dates to 27 Oct 2021. 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 binutils 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 binutils for upcoming vulnerabilities?

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