Skip to main content
Public proof of conceptFix available

CVE-2016-6328

A public proof of concept exists; no exploitation attested.

  • Published2018-10-31
  • WeaknessCWE-190

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability was found in libexif. An integer overflow when parsing the MNOTE entry data of the input file. This can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications' private data).

Timeline

dates in UTC
  1. 2018-10-3122:29CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-6328?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-6328?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Canonical ubuntu linux
BranchAffectedFixed in
12.4= 12.04no fix published
14.4= 14.04no fix published
16.4= 16.04no fix published
18.4= 18.04no fix published
19.10= 19.10no fix published
Debian debian linux
BranchAffectedFixed in
8.0= 8.0no fix published
Libexif project libexif
BranchAffectedFixed in
0.6< 0.6.220.6.22

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedPazhanivelmani/libexif_Android10_r33_CVE-2016-6328
PoC-in-GitHub

Sources

  • NVDCVSS 3.18.1read 2026-10-23
  • CNACVSS 3.06.1read 2026-10-23
  • NVDCVSS 2.05.8read 2026-10-23
  • CNAweakness (CWE)CWE-190read 2026-10-23
  • NVDweakness (CWE)CWE-190read 2026-10-23
  • FIRST EPSSEPSS score1.7 %2026-10-22
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Published
2018-10-31
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2016-6328?

A vulnerability was found in libexif. An integer overflow when parsing the MNOTE entry data of the input file. This can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications' private data).

Is CVE-2016-6328 actively exploited?

Active exploitation of CVE-2016-6328 has not been confirmed. Its EPSS score was 1.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-6328?

CVE-2016-6328 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H.

Running libexif? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month