Linux · Ubuntu · Package update · August 6, 2026

libavdevice58 7:4.4.2-0ubuntu0.22.04.1+esm16: libavdevice58 7:4.4.2-0ubuntu0.22.04.1+esm16 for Ubuntu 22.04.1 LTS (jammy)

libavdevice58 7:4.4.2-0ubuntu0.22.04.1+esm16, released August 6, 2026, fixes 7 CVEs in libavdevice58. None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
7
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0157
75th percentile

Priority of the 7 CVEs

Patch now 0 Urgent 0 High 2 Routine 5

Fixed package versions

ProductReleaseFixed in
libavdevice58Ubuntu 22.04.1 LTS (jammy)7:4.4.2-0ubuntu0.22.04.1+esm16

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-8461 ffmpeg: out-of-bounds write in the MagicYUV decoder can lead to denial of service or remote code execution8.8 0.0157 None reported
High CVE-2026-30999 ffmpeg: A heap buffer overflow in the av_bprint_finalize() function of FFmpeg v8.0.1 allows attackers to cause a Denial of Se...7.5 0.0046 None reported
Routine CVE-2026-58049 ffmpeg-4: incorrect validation in the RASC video decoder can lead to an out-of-bounds heap write and memoryn/a 0.0050 None reported
Routine CVE-2026-12706 ffmpeg-4: heap use-after-free read in the RASC video decoder can lead to denial of service (bsc#1268595).6.5 0.0045 None reported
Routine CVE-2026-70631 ffmpeg: FFmpeg versions from 0.5 up to, but not including, 9.0 contain an uninitialized heap memory disclosure vulnerability...n/a 0.0018 None reported
Routine CVE-2026-70629 ffmpeg: FFmpeg versions from 3.0 up to, but not including, 9.0 contain an uninitialized heap memory read vulnerability in the...n/a 0.0018 None reported
Routine CVE-2026-70630 ffmpeg: FFmpeg versions from 3.0 up to, but not including, 9.0 contain an uninitialized heap memory read vulnerability in the...n/a 0.0018 None reported
Showing 1 to 7 of 7 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.