Skip to content
Fencer Vulns
low 2.4

CVE-2021-27456 json

Philips Gemini PET/CT Storage of Sensitive Data in a Mechanism Without Access Control

published 2022-03-23 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-14210

cvss
2.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

Philips Gemini PET/CT family software stores sensitive information in a removable media device that does not have built-in access control.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-21-084-01 updated cvss 2.4

Philips Gemini PET/CT Family

  • Philips Gemini PET/CT Family 882300 Gemini 16 Slice, 882160 Gemini Dual, 882400 Gemini GXL 10 Slice, 882390 Gemini GXL 6 Slice
    affected: vendor fix usa.philips.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.4 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 2.4 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • Philips Gemini 16 Slice
  • Philips Gemini Dual
  • Philips Gemini GXL 10 Slice
  • Philips Gemini GXL 6 Slice
  • Philips Gemini GXL 16 Slice
  • Philips GEMINI LXL
  • Philips Gemini TF Ready
  • Philips Gemini TF 16 w/ TOF Performance
  • Philips Gemini TF 64 w/ TOF Performance
  • Philips Gemini TF Big Bore
  • Philips TruFlight Select PET/CT

Classification

Weakness
  • CWE-921 Storage of Sensitive Data in a Mechanism without Access Control
  • CWE-922 Insecure Storage of Sensitive Information

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.