Comparison Overview
Bioeconomy Corporation
Bioeconomy Corporation
Ground Floor, Menara Z10, Wilayah Persekutuan Putrajaya, 62000, MY
Last Update: 25/02/2026
Under the purview of MOSTI, Bioeconomy Corporation is owned by the Minister of Finance Incorporated and Federal Lands Commissioner, providing support, facilitation and advisory services for bio-based and life sciences companies in Malaysia. Bioeconomy Corporation facil...
Roche
Grenzacherstrasse, Switzerland 🇨🇭 , 4070, CH
Last Update: 28/06/2026
Roche is a global pioneer in pharmaceuticals and diagnostics focused on advancing science to improve people’s lives. The combined strengths of pharmaceuticals and diagnostics under one roof have made Roche the leader in personalised healthcare – a strategy that aims to ...
Compliance Ranges Comparison
Bioeconomy Corporation
Roche
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Bioeconomy Corporation in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Roche in 2026.
Incident History - Bioeconomy Corporation (X = Date, Y = Severity)
Bioeconomy Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Roche (X = Date, Y = Severity)
Roche cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bioeconomy Corporation
Roche
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.