Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
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-9082

cairo: Out of bounds read in read_png/write_png in cairo-png.c

Overview

Published
3 Feb 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
13 OS packages
5 Linux distributions
Yes Fix available

Description

Integer overflow in the write_png function in cairo 1.14.6 allows remote attackers to cause a denial of service (invalid pointer dereference) via a large svg file.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

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

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

Weakness: CWE-190

Affected packages · 0

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

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
cairo
Red Hat fixes for CVE-2016-9082
ReleasePackageFixed in
7 cairo +4 wont fix

debian 4 releases · 1 package

fixed 4
cairo
debian fixes for CVE-2016-9082
ReleasePackageFixed in
11 cairo 1.14.6-1.1
12 cairo 1.14.6-1.1
13 cairo 1.14.6-1.1
14 cairo 1.14.6-1.1

echo 1 release · 1 package

fixed 1
cairo
echo fixes for CVE-2016-9082
ReleasePackageFixed in
cairo 1.14.6-1.1

openSUSE 1 release · 1 package

fixed 1
cairo-devel
openSUSE fixes for CVE-2016-9082
ReleasePackageFixed inAdvisory
Tumbleweed cairo-devel +8 1.16.0-3.14 openSUSE-SU-2024:10671-1

root.io debian 2 releases · 1 package

fixed 2
rootio-cairo
root.io debian fixes for CVE-2016-9082
ReleasePackageFixed in
12 rootio-cairo 1.14.6-1.1
13 rootio-cairo 1.14.6-1.1

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.