ffjpeg commit caade60a69633d74100bd3c2528bddee0b6a1291 was discovered to contain a memory leak via /src/jfif.c.

published 2022-08-16 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-38321

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

Patch / fix

fixed in 1

ffjpeg_project ffjpeg 2021-12-16

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/rockcarry/ffjpeg/issues/52 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Classification

Weakness

CWE-401 Missing Release of Memory after Effective Lifetime

References

github.com /rockcarry/ffjpeg/issues/52
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2022-35433
NVD CVE-2022-35433

Fencer Vulns 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