Skip to main content
VulnerabilityPublished Updated

Matio: Use-of-uninitialized-value

Affects matioSource GCVE Database

0
Severity
Medium

Rated Medium by Threat Radar's AI analysis

Patch
Available – fixed in a8b4fd8d1ee7d98e0f4c84121432d1df5449332c, 3441ae35cacf4ca393a70a0ec97e7c68b430a76d

Data as of 15 Nov 2026, 15:38 UTC

What to do

Upgrade matio to a8b4fd8d1ee7d98e0f4c84121432d1df5449332c or 3441ae35cacf4ca393a70a0ec97e7c68b430a76d.

Affected software

ProductAffectedFixed in
OSS-Fuzzmatiopkg:generic/matioOther threatsAffected
  • >=ac1c67c687533d2de55f96709ed4512d4c197801 <3441ae35cacf4ca393a70a0ec97e7c68b430a76d
  • <a8b4fd8d1ee7d98e0f4c84121432d1df5449332c
  • =v1.6.0
Fixed in
  • 3441ae35cacf4ca393a70a0ec97e7c68b430a76d
  • a8b4fd8d1ee7d98e0f4c84121432d1df5449332c

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the vulnerability has been fixed in later versions of Matio as indicated by the referenced commits. Users should upgrade from version 1.6.0 to a fixed version to remediate this issue.

Description

A use-of-uninitialized-value vulnerability was identified in the Matio library version 1.6.0 within the ParseOpaqueMetadata function. This issue was reported by OSS-Fuzz and results in a crash due to reading uninitialized memory. The vulnerability has been addressed in subsequent commits.

References

Community reviews

Loading reviews…