A use-after-free vulnerability exists in the way MKVToolNix MKVINFO v25.0.0 handles the MKV (matroska) file format.

published 2018-10-26 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-15808

cvss: 7.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

A use-after-free vulnerability exists in the way MKVToolNix MKVINFO v25.0.0 handles the MKV (matroska) file format. A specially crafted MKV file can cause arbitrary code execution in the context of the current user.

Patch / fix

distros 1

mkvtoolnix Debian 14, Debian 13, Debian 12 28.2.0-1

debian advisories DEBIAN-CVE-2018-4022

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-4022 updated 2026-01-09 cvss 7.3

mkvtoolnix: MKVINFO read_one_element code execution vulnerability

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2018-0694 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.3	CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

n/a MKVToolNix

Classification

Weakness

CWE-416 Use After Free

References

talosintelligence.com /vulnerability_reports/TALOS-2018-0694
exploit, third-party-advisory

Sources

CVE List CVE-2018-4022
NVD CVE-2018-4022

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary