Philips Brilliance CT software (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and prior, Brillance iCT SP versions 3…

published 2018-05-04 8y ago modified 2026-06-17 4mo ago also EUVD-2018-20465

cvss: 7.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

Philips Brilliance CT software (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and prior, Brillance iCT SP versions 3.2.4 and prior, and Brilliance CT Big Bore 2.3.5 and prior) contains fixed credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. An attacker could compromise these credentials and gain access to the system.

Is CVE-2018-8857 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSMA-18-123-01 updated 2019-10-10 cvss 8.4

Philips Brilliance Computed Tomography (CT) System (Update A)

Philips Brilliance 64 <=2.6.2 Philips Brilliance CT Big Bore <=2.3.5 Philips Brilliance iCT <=4.1.6, <=3.2.4
affected: vendor fix incenter.medical.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

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

Philips Brilliance CT Scanners

Classification

Weakness

CWE-798 Use of Hard-coded Credentials

References

usa.philips.com /healthcare/about/customer-support/product-security
vendor-advisory
securityfocus.com /bid/104088
vdb-entry, third-party-advisory
ics-cert.us-cert.gov /advisories/ICSMA-18-123-01
third-party-advisory, us-government-resource

Sources

CVE List CVE-2018-8857
NVD CVE-2018-8857

Fencer Intel 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.