# CVE-2025-15647: CDT before 1.4.5 Out-of-Bounds Read via opposedVertexInd

> Attackers can crash the application by supplying nearly-degenerate constraint edges to the CDT library, causing an out-of-bounds read.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-gg9p-3jmx-h6rw

## What is CVE-2025-15647?

CVE-2025-15647 is a medium-severity memory corruption vulnerability in artem-ogre CDT, published on 5 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

CDT before 1.4.5 contains an out-of-bounds read vulnerability in the opposedVertexInd() function when constraint edge intersections are computed in floating point and round outside adjacent triangles. Attackers can supply nearly-degenerate constraint edges through geometry data to trigger an out-of-bounds array access that crashes the calling process.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2025-15647 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15647 is a medium-severity memory corruption vulnerability in artem-ogre CDT, published on 5 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15647 exists.

Affected product: artem-ogre CDT. 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-15647/ (Markdown: https://insights.sbomify.com/CVE-2025-15647/index.md)
```

## Sources

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

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