# CVE-2025-29070: Memory corruption in n/a

> A heap buffer overflow in the lcms2 library allows remote attackers to cause a denial of service via the smooth2 function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** AZL-59467, AZL-61816, DEBIAN-CVE-2025-29070, ECHO-5806-b837-d9a0, GHSA-qgv4-vprj-x2fq, ROOT-OS-DEBIAN-12-CVE-2025-29070

## What is CVE-2025-29070?

CVE-2025-29070 is a high-severity memory corruption vulnerability in n/a, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap buffer overflow vulnerability has been identified in thesmooth2() in cmsgamma.c in lcms2-2.16 which allows a remote attacker to cause a denial of service. NOTE: the Supplier disputes this because "this is not exploitable as this function is never called on normal color management, is there only as a helper for low-level programming and investigation."

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

No fix published yet.

## Is CVE-2025-29070 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29070 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29070 is a high-severity memory corruption vulnerability in n/a, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29070 exists.

Affected product: n/a. 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-29070/ (Markdown: https://insights.sbomify.com/CVE-2025-29070/index.md)
```

## Sources

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

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