Comparison Overview
Novocure
Novocure
Neuhofstrasse 21, Baar, 6340, CH
Last Update: 01/09/2026
Novocure is a global oncology company working to extend survival in some of the most aggressive forms of cancer through the development and commercialization of its innovative therapy, Tumor Treating Fields. Novocure’s commercialized products are approved in certain co...
B. Braun Group
Carl-Braun-Straße 1, Melsungen, DE, 34212
Last Update: 08/09/2026
As a leading medical technology company, B. Braun protects and improves the health of people around the world. For more than 185 years, the family-owned company has been accelerating progress in health care with pioneering spirit and groundbreaking contributions. This i...
Compliance Ranges Comparison
Novocure
B. Braun Group
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Novocure has 8.26% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for B. Braun Group in 2026.
Incident History - Novocure (X = Date, Y = Severity)
Novocure cyber incidents detection timeline including parent company and subsidiaries.
Incident History - B. Braun Group (X = Date, Y = Severity)
B. Braun Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Novocure
B. Braun Group
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout