Skip to main content
VulnerabilityPublished Updated

CVE-2025-28162: libpng · Buffer Overflow

Affects libpngSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubpnggroup/libpngpkg:github/pnggroup/libpngOther threatsAffected
  • 1.6.43 – 1.6.46
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific mitigation steps: 1) Identify and inventory all systems and applications using libpng versions 1.6.43 to 1.6.46, especially those with AddressSanitizer enabled. 2) Apply patches or upgrade libpng to versions beyond 1.6.46 once available from trusted sources. 3) Restrict local user permissions to prevent untrusted users from executing or providing malicious PNG files to vulnerable applications. 4) Disable AddressSanitizer in production environments unless explicitly required, as it increases exposure to this vulnerability. 5) Implement monitoring for abnormal memory usage patterns in applications processing PNG images to detect potential exploitation attempts. 6) Educate developers and system administrators about the risks of running ASan-enabled binaries in production. 7) Use application whitelisting and file integrity monitoring to prevent unauthorized PNG files from being processed. These targeted actions go beyond generic advice by focusing on the specific conditions that enable exploitation.

Description

Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via the pngimage with AddressSanitizer (ASan), the program leaks memory in various locations, eventually leading to high memory usage and causing the program to become unresponsive

References

Community reviews

Loading reviews…