Application crash via unchecked DBF field length
Published Jan 18, 2026 · Updated Jan 18, 2026
Heap-based buffer over-read in Mapnik 4.2.0 and earlier allows local users to crash applications by processing a malformed shapefile. In dbf_file::string_value, a DBF-header-derived offset and length reach the std::string constructor without validation against the allocated buffer. Exploitation requires local processing of attacker-controlled shapefile data; the demonstrated consequence is a SIGABRT process crash.
Summary
What happened
Heap-based buffer over-read in Mapnik 4.2.0 and earlier allows local users to crash applications by processing a malformed shapefile. In dbf_file::string_value, a DBF-header-derived offset and length reach the std::string constructor without validation against the allocated buffer. Exploitation requires local processing of attacker-controlled shapefile data; the demonstrated consequence is a SIGABRT process crash.
The record
- CVE
- CVE-2025-15537
- Published
- Jan 18, 2026
- Updated
- Jan 18, 2026
- Vendor
- Mapnik
- Product
- Mapnik
- Classifications
- CWE-119, CWE-787, CWE-122
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2026CVE publishedPublication date reported by the CVE source.
- Jan 18, 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=4.0
- Affected versionversion=4.1
- Affected versionversion=4.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Mapnik malformed DBF crashing-file reproducerproof 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