VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2025-15564: Mapnik · Divide By Zero

Affects MapnikSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mapnik	Affected =4.0 =4.1 =4.2.0	Fixed in–
GitHubmapnik/mapnik`pkg:github/mapnik/mapnik`Other threats	Affected =4.0 =4.1 =4.2.0	Fixed in–

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

AI-suggested

To mitigate CVE-2025-15564, organizations should first restrict local access to systems running vulnerable Mapnik versions to trusted users only. Implement strict access controls and monitoring to detect suspicious local activity. Review and harden the input validation logic in Mapnik source code if feasible, or apply community patches if available. Employ application-level monitoring to detect crashes or abnormal behavior indicative of exploitation attempts. For development environments, rebuild Mapnik from source with added checks to prevent divide-by-zero operations. Maintain close communication with the Mapnik project for updates and apply patches promptly once released. Additionally, educate local users about the risks of running untrusted code or inputs that could trigger this vulnerability.

Description

A vulnerability has been found in Mapnik up to 4.2.0. This vulnerability affects the function mapnik::detail::mod<...>::operator of the file src/value.cpp. The manipulation leads to divide by zero. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2025-15564 is denial of service caused by application crashes due to the divide-by-zero error. This can disrupt local services or processes relying on Mapnik, potentially affecting availability of mapping or geospatial data rendering. Since exploitation requires local access, remote attackers cannot directly exploit this vulnerability, limiting its scope. Confidentiality and integrity of data are not compromised by this flaw. However, in environments where Mapnik is integrated into critical workflows or automated systems, repeated crashes could lead to operational disruptions and increased maintenance overhead. The public availability of exploit code increases the risk of insider threats or malicious local users leveraging this vulnerability. Organizations with Mapnik deployed on user workstations or servers should consider the risk of local denial of service and potential impact on service continuity.

Summary

CVE-2025-15564 identifies a divide-by-zero vulnerability in the Mapnik open-source mapping toolkit, specifically affecting versions 4.0 through 4.2.0. The flaw exists in the implementation of the modulo operator function (mapnik::detail::mod<...>::operator) located in the source file src/value.cpp. When certain inputs are manipulated locally, the function attempts to perform a modulo operation with zero as the divisor, causing a divide-by-zero error. This results in an unhandled exception that can crash the application or cause denial of service. The vulnerability requires local access with low privileges, does not require user interaction, and does not affect confidentiality or integrity of data. The CVSS 4.0 base score is 4.8, reflecting a medium severity due to limited attack vector and impact scope. Public exploit code has been disclosed, increasing the risk of local exploitation. The vulnerability is relevant to any organization running Mapnik locally, especially in GIS, mapping, or geospatial data processing environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:47 UTC

Technical details

References

Community reviews

Related threats