Vulnerability Database · OSS-Fuzz · Package report

md4c: vulnerability history, versions and safety

md4c is a package in the OSS-Fuzz ecosystem. Vulert records 14 vulnerabilities for it across 3 releases, from Jan 2022 to Sep 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 H5 M7 U2
i
2 with no fix published

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

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

Most recent disclosure 16 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on md4c i

Updated on 23 Oct 2026

Careful: 2 of the 14 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 14 vulnerabilities on record across 4 years, 10 in the last year.

What to do: Plan around the 2 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 14 over 4 years · 10 in the last year i
  • Latest disclosure 16 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 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 md4c, 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.

i
Version Vulert vulnerabilities Fix published Details
release-0.5.2 M1 No Details →
release-0.5.1 M1 No Details →
release-0.5.0 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for md4c

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in md4c Package N/A medium 60965ab9ab0e0b69a091d493631feffd09a8f908 14 Sep 2026
Heap Buffer Overflow Vulnerability in md4c Package N/A medium b8d9ee1135b8f7f26df3e86a7afb04a0ccbc55b9 17 May 2026
Heap Buffer Overflow Vulnerability in md4c Package N/A high b8d9ee1135b8f7f26df3e86a7afb04a0ccbc55b9 19 May 2026
Heap Buffer Overflow Vulnerability in md4c Package N/A medium fb4d03dfda4e4e0c24f9a1b43ccd2dacab2bd190 27 May 2026
Global Buffer Overflow Vulnerability in md4c Package N/A unrated 5f9b246fd01e90afa8075c1b6c2904ea44375fe3 14 May 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 md4c

Is md4c safe to use?

Vulert records 14 vulnerabilities for md4c in OSS-Fuzz: 0 critical, 5 high, 7 medium and 0 low, plus 2 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does md4c have?

14 vulnerabilities are recorded for md4c in the OSS-Fuzz ecosystem: 0 critical, 5 high, 7 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 md4c vulnerabilities disclosed?

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

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