# CVE-2025-66909: Denial of service in n/a

> Attackers can crash the AI serving service by uploading crafted compressed images that cause memory exhaustion, requiring no authentication if the service is public.

- **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:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-2f87-396w-g74p

## What is CVE-2025-66909?

CVE-2025-66909 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Turms AI-Serving module v0.10.0-SNAPSHOT and earlier contains an image decompression bomb denial of service vulnerability. The ExtendedOpenCVImage class in ai/djl/opencv/ExtendedOpenCVImage.java loads images using OpenCV's imread() function without validating dimensions or pixel count before decompression. An attacker can upload a specially crafted compressed image file (e.g., PNG) that is small when compressed but expands to gigabytes of memory when loaded. This causes immediate memory exhaustion, OutOfMemoryError, and service crash. No authentication is required if the OCR service is publicly accessible. Multiple requests can completely deny service availability.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

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

It affects 1 product.


Products: Turms-Im Turms.

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

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

## Is CVE-2025-66909 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-66911](https://insights.sbomify.com/CVE-2025-66911/): Missing authorization in n/a (medium 6.5)
- [CVE-2025-66906](https://insights.sbomify.com/CVE-2025-66906/): Cross-site request forgery in n/a (medium 6.1)
- [CVE-2025-66910](https://insights.sbomify.com/CVE-2025-66910/): Information disclosure in n/a (medium 6.0)
- [CVE-2025-66908](https://insights.sbomify.com/CVE-2025-66908/): File upload in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66909 is a high-severity denial of service vulnerability in n/a, published on 19 Dec 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-66909 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-66909/ (Markdown: https://insights.sbomify.com/CVE-2025-66909/index.md)
```

## Sources

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

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