CVE-2025-50343 DO NOT USE THIS CVE RECORD.
Not scored
Published
Updated
Check this codebase for CVE-2025-50343 and fix it if it is affected.
What it is: CVE-2025-50343 is a memory corruption vulnerability in matio, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50343 in the wild and no public exploit code.
Affected product: matio. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-50343/ (Markdown: https://insights.sbomify.com/CVE-2025-50343/index.md)
Heap-based memory corruption in MATIO library can cause segmentation faults or crashes when processing malformed struct fields.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-50343?
CVE-2025-50343 is a memory corruption vulnerability in matio, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Which versions are affected by CVE-2025-50343?
Linux distribution packages (1)
matio openSUSE:Tumbleweed | All versions | 1.5.30-1.1 |
How do I fix CVE-2025-50343?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-50343 being exploited?
There is no known exploitation of CVE-2025-50343 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2025-50343, GHSA-54r5-8767-w6vq, UBUNTU-CVE-2025-50343, openSUSE-SU-2026:10094-1.