# CVE-2026-107621: J4Care dcm4che Loop with Unreachable Exit Condition

> Attackers can cause a denial of service in dcm4chee-arc-light by sending crafted or truncated JPEG streams that trigger an infinite loop.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026

## What is CVE-2026-107621?

CVE-2026-107621 is a high-severity denial of service vulnerability in J4Care dcm4chee-arc-light, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JPEGParser can enter an infinite loop while parsing a specially crafted or truncated stream.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-107621?


## How do I fix CVE-2026-107621?

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

## Is CVE-2026-107621 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107621 and fix it if it is affected.

What it is: CVE-2026-107621 is a high-severity denial of service vulnerability in J4Care dcm4chee-arc-light, published on 16 Oct 2026. 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-2026-107621 in the wild and no public exploit code.

Affected product: J4Care dcm4chee-arc-light. 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-2026-107621/ (Markdown: https://insights.sbomify.com/CVE-2026-107621/index.md)
```

## Sources

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

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