Comparison Overview
Demant

Demant
Kongebakken 9, Smørum, 2765, DK
Last Update: 06/07/2026
Demant is a world-leading hearing healthcare group built on a heritage of care, health and innovation since 1904. The Group offers solutions and services to help people connect and communicate with the world around them. For more than a century, the Demant Group has pla...

BD
1 Becton Drive, Franklin Lakes, 07417, US
Last Update: 03/09/2026
BD is one of the world's largest pure-play medical technology companies with a Purpose of advancing the world of health™ by driving innovation across medical essentials, connected care, biopharma systems and interventional. The company supports those on the frontlines o...
Compliance Ranges Comparison

Demant







BD






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Demant in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for BD in 2026.
Incident History - Demant (X = Date, Y = Severity)
Demant cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BD (X = Date, Y = Severity)
BD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Demant

BD
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.