Safeguard
Vulnerability Analysis•

CVE-2021-40367: High DICOM Write Flaw in syngo fastView

CVE-2021-40367 is a high out-of-bounds write in syngo fastView DICOM parsing, scored 7.8. No fix is planned, so apply the Siemens workarounds or remove it.

Safeguard Security Team
4 min read

CVE-2021-40367 is a high severity out-of-bounds write in how Siemens syngo fastView parses DICOM files, scored 7.8. It affects all versions, and Siemens Healthineers says no remediation is currently planned. Apply the vendor workarounds, avoid untrusted files, and remove the viewer when you no longer need it.

What's affected

The record and the advisory describe a lack of validation of user supplied data when parsing DICOM files. That can lead to an out-of-bounds write past the end of an allocated structure, and an attacker could use it to run code in the context of the current process. The vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, a local attack with user interaction.

Siemens Healthineers advisory SHSA-688797 was first published on 2021-12-14 and updated on 2022-02-08, when CVE-2021-45465 was added. It lists syngo fastView as affected in all versions, and says that currently no remediation is planned. That is the key fact for planning: there is no fixed version to move to.

The advisory scores the issue 7.8, the same as the NVD record, so the two sources agree on severity. The advisory notes that syngo fastView is a standalone viewer for DICOM images from exchange media, that it can run on any Windows PC, and that it is not a medical device and not permitted for diagnostic use.

Weakness class: CWE-787.

How to check if you're exposed

There is no patch to look for, so the check is whether the software is installed at all. Search your Windows endpoint inventory, or the installed programs list, for syngo fastView.

If it is present, find out who uses it and what files they open with it. The advisory describes a risk from a user opening a malicious file, so the people who receive DICOM media or images from outside are the ones most exposed.

Siemens says the product cannot run on its own medical workstations, so the places to look are ordinary Windows PCs, for example in reception, referral or research settings.

What to do now

  1. Search for syngo fastView across your endpoints and record every install.
  2. Apply the Siemens Healthineers workarounds: download the viewer only from the official page, avoid opening untrusted files from unknown sources, and remove it after viewing the files you need.
  3. Treat DICOM media from outside your organisation as untrusted and open it on a machine with limited access.
  4. Contact your Siemens Healthineers Customer Service Engineer for product specific guidance, as the advisory suggests.

Why it matters

DICOM is the standard format for medical images, and the files are complex, with many fields whose sizes a parser has to check. When code trusts a length or an index that comes from the file, a crafted file can make it write outside the buffer it allocated. The record files this under CWE-787, out-of-bounds write.

The attack needs a person to open the file, and the code runs with that person's rights, not as a system service. Even so, a clinical or research workstation often has access to patient data. An out-of-bounds write is the class most often turned into code execution.

Because there is no vendor fix, compensating controls carry the whole load. Limit where the viewer is installed, control where files come from, and keep the application out of workflows that touch untrusted media.

This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.

Quick check

Is there a patch for CVE-2021-40367?

Not according to the advisory. Siemens Healthineers lists all versions as affected and says that currently no remediation is planned, with workarounds instead.

Does opening a file trigger it?

Yes. The advisory says a user who is tricked into opening a malicious file could cause a crash or code execution.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.