Mapnik up to 4.2.0 dbfile.cpp string_value heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Mapnik up to 4.2.0. Impacted is the function mapnik::dbf_file::string_value of the file plugins/input/shape/dbfile.cpp. Performing a manipulation results in heap-based overflow.
This vulnerability is cataloged as CVE-2025-15537. The attack must be initiated from a local position. Furthermore, there is an exploit available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in Mapnik up to 4.2.0. It has been classified as critical. This affects the function mapnik::dbf_file::string_value of the file plugins/input/shape/dbfile.cpp. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-15537. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-3179). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
- Product: https://github.com/mapnik/mapnik/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CNA Base Score: 5.3
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/17/2026 Advisory disclosed01/17/2026 VulDB entry created
02/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 4543
Status: Not defined
CVE: CVE-2025-15537 (🔒)
GCVE (CVE): GCVE-0-2025-15537
GCVE (VulDB): GCVE-100-341709
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/17/2026 17:34Updated: 02/07/2026 00:23
Changes: 01/17/2026 17:34 (56), 01/18/2026 11:39 (30), 01/18/2026 23:57 (1), 02/07/2026 00:23 (11)
Complete: 🔍
Submitter: Oneafter
Cache ID: 216::103
Submit
Accepted
- Submit #733348: mapnik Mapnik v4.2.0 and master-branch Heap-based Buffer Overflow (by Oneafter)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.