Local process memory corruption via wrapped row-size calculation
Published Mar 8, 2026 · Updated Mar 8, 2026
Heap-based buffer overflow in libpng pnm2png 1.6.0 through 1.6.55 allows local users to corrupt process memory via a crafted PNM file. In do_pnm2png, a 32-bit row_bytes multiplication wraps to a small nonzero value, passes the size guard, and allocates an undersized row buffer while the pixel loop writes according to the original width and channel count. Exploitation requires local execution of the ancillary pnm2png converter against attacker-controlled input and can crash or corrupt that process.
Summary
What happened
Heap-based buffer overflow in libpng pnm2png 1.6.0 through 1.6.55 allows local users to corrupt process memory via a crafted PNM file. In do_pnm2png, a 32-bit row_bytes multiplication wraps to a small nonzero value, passes the size guard, and allocates an undersized row buffer while the pixel loop writes according to the original width and channel count. Exploitation requires local execution of the ancillary pnm2png converter against attacker-controlled input and can crash or corrupt that process.
The record
- CVE
- CVE-2026-3713
- Published
- Mar 8, 2026
- Updated
- Mar 8, 2026
- Vendor
- PNG Development Group
- Product
- libpng
- Classifications
- CWE-122, CWE-119, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 8, 2026CVE publishedPublication date reported by the CVE source.
- Mar 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.6.0
- Affected versionversion=1.6.1
- Affected versionversion=1.6.10
- Affected versionversion=1.6.11
- Affected versionversion=1.6.12
- Affected versionversion=1.6.13
- Affected versionversion=1.6.14
- Affected versionversion=1.6.15
- Affected versionversion=1.6.16
- Affected versionversion=1.6.17
- Affected versionversion=1.6.18
- Affected versionversion=1.6.19
- Affected versionversion=1.6.2
- Affected versionversion=1.6.20
- Affected versionversion=1.6.21
- Affected versionversion=1.6.22
- Affected versionversion=1.6.23
- Affected versionversion=1.6.24
- Affected versionversion=1.6.25
- Affected versionversion=1.6.26
- Affected versionversion=1.6.27
- Affected versionversion=1.6.28
- Affected versionversion=1.6.29
- Affected versionversion=1.6.3
- Affected versionversion=1.6.30
- Affected versionversion=1.6.31
- Affected versionversion=1.6.32
- Affected versionversion=1.6.33
- Affected versionversion=1.6.34
- Affected versionversion=1.6.35
- Affected versionversion=1.6.36
- Affected versionversion=1.6.37
- Affected versionversion=1.6.38
- Affected versionversion=1.6.39
- Affected versionversion=1.6.4
- Affected versionversion=1.6.40
- Affected versionversion=1.6.41
- Affected versionversion=1.6.42
- Affected versionversion=1.6.43
- Affected versionversion=1.6.44
- Affected versionversion=1.6.45
- Affected versionversion=1.6.46
- Affected versionversion=1.6.47
- Affected versionversion=1.6.48
- Affected versionversion=1.6.49
- Affected versionversion=1.6.5
- Affected versionversion=1.6.50
- Affected versionversion=1.6.51
- Affected versionversion=1.6.52
- Affected versionversion=1.6.53
- Affected versionversion=1.6.54
- Affected versionversion=1.6.55
- Affected versionversion=1.6.6
- Affected versionversion=1.6.7
- Affected versionversion=1.6.8
- Affected versionversion=1.6.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- pnm2png integer-overflow PNM proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo