How do I check whether I am affected by CVE-2026-107621?

Check the installed dcm4chee-arc-light version (archive UI or deployment image tag). 5.35.1 is affected per CISA; earlier versions are not confirmed either way. Exposed if the archive accepts DICOM or upload traffic from untrusted networks.

What is the fix for CVE-2026-107621?

Upgrade dcm4chee-arc-light to 5.35.2 or later (J4Care's fix per CISA ICSMA-26-288-02). Until then, keep the archive off the internet and behind a firewall or VPN.

Who is not affected by CVE-2026-107621?

Not affected if: no-untrusted-jpeg-input, not-network-exposed.

Live › vulnerability › CVE-2026-107621

Go to dashboard

high8.7Package

JPEGParser: crafted or truncated JPEG stream causes infinite loop

The JPEGParser in J4Care dcm4chee-arc-light (a DICOM medical image archive) can loop forever on a crafted or truncated JPEG stream. A remote unauthenticated sender can pin CPU and make the archive unresponsive (CWE-835). It is one of six flaws fixed together in 5.35.2.

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

8.7

high

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 24, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Parser hangs forever on a crafted file, stalling the service.
CVSS said: 8.7. The facts above say low; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-107621

Go to dashboard

high8.7Package

JPEGParser: crafted or truncated JPEG stream causes infinite loop

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

8.7

high

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 24, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Parser hangs forever on a crafted file, stalling the service.
CVSS said: 8.7. The facts above say low; we keep the sources' high until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

JPEGParser: crafted or truncated JPEG stream causes infinite loop

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

JPEGParser: crafted or truncated JPEG stream causes infinite loop

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources