Comparison Overview
Roche Danmark

Roche Danmark
Flaskehalsen 17, 4, Copenhagen, 1799, DK
Last Update: 13/02/2026
Velkommen til Roche Danmarks LinkedIn profil. En sundere fremtid. Det er vores motivation. Derfor har vi engageret os i danskernes sundhed gennem samarbejde med aktørerne i det danske sundhedsvæsen i mere end 50 år. Med fokus på samlede forløb tilbyder vi digitale ...

Charles River Laboratories
251 Ballardvale Street, Wilmington, Massachusetts, US, 01887
Last Update: 11/09/2026
At Charles River, we are guided by our strong purpose—to create healthier lives—which centers around the patients who rely on the therapeutics we help to develop, the animals in our care, to our planet, and to the passionate and skilled people who are at the heart of ou...
Compliance Ranges Comparison

Roche Danmark







Charles River Laboratories






Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Roche Danmark in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Charles River Laboratories in 2026.
Incident History - Roche Danmark (X = Date, Y = Severity)
Roche Danmark cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Charles River Laboratories (X = Date, Y = Severity)
Charles River Laboratories cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Roche Danmark

Charles River Laboratories
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)