VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

matio: vulnerability history, versions and safety

matio is a package in the OSS-Fuzz ecosystem. Vulert records 71 vulnerabilities for it across 17 releases, from Jul 2020 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
71 vulnerabilities recorded H13 M55 U3
i
11 with no fix published

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

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

Most recent disclosure 14 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all matio vulnerabilities

Vulert verdict on matio i

Updated on 23 Oct 2026

Careful: 11 of the 71 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 71 vulnerabilities on record across 6 years, 11 in the last year.

What to do: Plan around the 11 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 71 over 6 years · 11 in the last year i
  • Latest disclosure 14 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 11 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 matio, 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
v1.6.0 M1 Yes Details →
v1.5.30 M2 Yes Details →
v1.5.28 H1 M8 No Details →
v1.5.27 H1 M9 No Details →
v1.5.26 H2 M8 No Details →
v1.5.25 H2 M8 No Details →
v1.5.24 H2 M8 No Details →
v1.5.23 H2 M4 No Details →
v1.5.22 H2 M10 U1 No Details →
v1.5.21 H4 M10 U1 No Details →
v1.5.20 H4 M10 U1 No Details →
v1.5.19 H5 M17 U1 No Details →
v1.5.18 H5 M17 U1 No Details →
v1.5.17 M5 Yes Details →
v1.5.16 M2 Yes Details →
v1.5.15 M1 Yes Details →
v1.5.14 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 25
  • 2021 22
  • 2023 6
  • 2024 7
  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for matio

The 5 most severe of 71 vulnerabilities recorded for this package

Search all 71 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in H5O__sdspace_decode in matio N/A medium 2f19958fade08de870257f099d88ecc813ab623f 13 Jan 2021
OSV-2026-1279: Heap-buffer-overflow read in matio N/A medium fe19d779aa324f1b1a025d4287afcd5740d12522 14 Sep 2026
Heap-buffer-overflow in H5O__cont_decode in matio N/A medium b89ed176f27c71657587d231794bee09d0461d08 13 Jan 2021
Heap-buffer-overflow in Mat_VarDuplicate N/A medium b6219380c57afa91e9357ff09a33866237748d30 17 Apr 2024
Heap-buffer-overflow in H5MM_strdup in matio N/A medium 8195e5d3e3c65ff6bcc0aae31a4a53eb609c4d7e 13 Jan 2021

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 matio

Is matio safe to use?

Vulert records 71 vulnerabilities for matio in OSS-Fuzz: 0 critical, 13 high, 55 medium and 0 low, plus 3 not yet rated. 11 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does matio have?

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

11 vulnerabilities were recorded for matio in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. 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 matio 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 matio for upcoming vulnerabilities?

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