Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-2327

libavcodec/pngenc.c in FFmpeg before 2.8.5 uses incorrect line sizes i ...

Overview

Published
12 Feb 2016
Modified
17 Jun 2026
High CVE
0 Registry packages
2 OS packages
4 Linux distributions
Yes Fix available

Description

libavcodec/pngenc.c in FFmpeg before 2.8.5 uses incorrect line sizes in certain row calculations, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via a crafted .avi file, related to the apng_encode_frame and encode_apng functions.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

debian 4 releases · 1 package

fixed 4
ffmpeg
debian fixes for CVE-2016-2327
ReleasePackageFixed in
11 ffmpeg 2.8.5-1
12 ffmpeg 2.8.5-1
13 ffmpeg 2.8.5-1
14 ffmpeg 2.8.5-1

echo 1 release · 1 package

fixed 1
ffmpeg
echo fixes for CVE-2016-2327
ReleasePackageFixed in
ffmpeg 2.8.5-1

root.io debian 2 releases · 1 package

fixed 2
rootio-ffmpeg
root.io debian fixes for CVE-2016-2327
ReleasePackageFixed in
11 rootio-ffmpeg 2.8.5-1
12 rootio-ffmpeg 2.8.5-1

ubuntu 2 releases · 1 package

fixed 2
ffmpeg
ubuntu fixes for CVE-2016-2327
ReleasePackageFixed in
18.04 ffmpeg 7:2.8.6-1ubuntu1
18.04-ESM ffmpeg 7:2.8.6-1ubuntu1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.