VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

bloaty: vulnerability history, versions and safety

bloaty is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 3 affected ranges, from Jan 2021 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M1 U1
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bloaty vulnerabilities

Vulert verdict on bloaty i

Updated on 23 Oct 2026

Careful: one of the 3 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 3 over 4 years · 0 in the last year i
  • Latest disclosure 13 Feb 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 0120168db4ba908b11545f19b08aea8afbbe9bc1 up to 18384d6c6cbb666d08d08c0dabc4a0d1b7623f6f (exclusive) 1
from 1c10c64cc9bb31a61e7f6d0d015794fa9dd904dd up to 3028ca5e4ab5ad883d3b6246ba587d6c71d89766 (exclusive) 1
from 752f32eb40510b064ba47cefd4125a162b348e43 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for bloaty

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in bloaty::DisassembleFindReferences N/A medium 18384d6c6cbb666d08d08c0dabc4a0d1b7623f6f 13 Jan 2021
Global-buffer-overflow in bloaty::wasm::Section::Read N/A unrated 3028ca5e4ab5ad883d3b6246ba587d6c71d89766 13 Jan 2021
Critical Stack Buffer Overflow in Bloaty Package N/A high No fix published 13 Feb 2025

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 bloaty

Is bloaty safe to use?

Vulert records 3 vulnerabilities for bloaty in OSS-Fuzz: 0 critical, 1 high, 1 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does bloaty have?

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

0 vulnerabilities were recorded for bloaty in the last 12 months, and the oldest entry in this database dates to 13 Jan 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 bloaty 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 bloaty for upcoming vulnerabilities?

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