# CVE-2025-4640: Out-of-bounds Write in pcl

> An out-of-bounds write in Point Cloud Library allows attackers to cause memory corruption, potentially leading to code execution or crashes.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/AU:Y/R:U/V:C/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2025
- **Updated:** 15 May 2025
- **Also known as:** GHSA-vrqw-478g-gv6h, UBUNTU-CVE-2025-4640

## What is CVE-2025-4640?

CVE-2025-4640 is a high-severity memory corruption vulnerability in PointCloudLibrary pcl, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out-of-bounds Write vulnerability in PointCloudLibrary pcl allows Overflow Buffers. Since version 1.14.0, PCL by default uses a zlib installation from the system, unless the user sets WITH_SYSTEM_ZLIB=FALSE. So this potential vulnerability is only relevant if the PCL version is older than 1.14.0 or the user specifically requests to not use the system zlib.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

No fix has been published for CVE-2025-4640 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4640 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4640 is a high-severity memory corruption vulnerability in PointCloudLibrary pcl, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4640 in the wild and no public exploit code.

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

## Sources

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

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