Skip to content
Fencer Intel
critical 9.8

CVE-2015-7700 json

Double-free vulnerability in the sPLT chunk structure and png.c in pngcrush before 1.7.87 allows attackers to have unspecified impact via u…

published 2017-08-31 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7601

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Double-free vulnerability in the sPLT chunk structure and png.c in pngcrush before 1.7.87 allows attackers to have unspecified impact via unknown vectors.

Patch / fix

  • pngcrush Debian 14, Debian 13, Debian 12 1.8.13-0.1

debian advisories DEBIAN-CVE-2015-7700

  • pngcrush Ubuntu Pro 16.04 LTS 1.7.85-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2015-7700

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • pngcrush openSUSE Tumbleweed 1.7.92-1.5

opensuse advisories openSUSE-SU-2024:10351-1

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-2015-7700 updated cvss 3.3

pngcrush: double-free in sPLT and png.c file

  • Red Hat Enterprise Linux 7 pngcrush
    affected: no fix planned “Will not fix”

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

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

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

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.