# CVE-2025-52937: Vulnerability in PointCloudLibrary PCL

> Attackers can exploit a bundled third-party component in older PCL versions or non-default builds to potentially execute arbitrary code.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/S:N/AU:N/R:A/V:D/RE:M/U:Green`)
- **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:** No
- **Published:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-2fqm-p827-242q, UBUNTU-CVE-2025-52937

## What is CVE-2025-52937?

CVE-2025-52937 is a low-severity vulnerability in PointCloudLibrary pcl, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in PointCloudLibrary PCL (surface/src/3rdparty/opennurbs modules). This vulnerability is associated with program files crc32.C.

This 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 (WITH_SYSTEM_ZLIB=FALSE).

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2025-52937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52937 is a low-severity vulnerability in PointCloudLibrary pcl, published on 23 Jun 2025. 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-52937 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-52937/ (Markdown: https://insights.sbomify.com/CVE-2025-52937/index.md)
```

## Sources

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

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