# CVE-2025-15564: Mapnik value.cpp operator divide by zero

> A local attacker can cause a denial of service in the Mapnik library via a divide-by-zero error in value.cpp, requiring local access to exploit.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-15564, GHSA-4r58-h5cf-8qgj, UBUNTU-CVE-2025-15564

## What is CVE-2025-15564?

CVE-2025-15564 is a medium-severity denial of service vulnerability in Mapnik, published on 7 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2025-15564?

It affects 1 product.


Products: Mapnik Mapnik.

## How do I fix CVE-2025-15564?

No fix published yet.

## Is CVE-2025-15564 being exploited?

There is no known exploitation of CVE-2025-15564 in the wild and no public exploit code.

## Other vulnerabilities in Mapnik

- [CVE-2025-15537](https://insights.sbomify.com/CVE-2025-15537/): Mapnik dbfile.cpp string_value heap-based overflow (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15564 and fix it if it is affected.

What it is: CVE-2025-15564 is a medium-severity denial of service vulnerability in Mapnik, published on 7 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15564 in the wild and no public exploit code.

Affected product: Mapnik. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15564/ (Markdown: https://insights.sbomify.com/CVE-2025-15564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15564
- OSV: https://osv.dev/vulnerability/CVE-2025-15564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15564/
Summaries are generated and may contain mistakes; the official description above is the record.