Comparison Overview
SHIMADZU CORPORATION
SHIMADZU CORPORATION
1,Nishinokyo-Kuwabara-cho, Nakagyo-ku,, Kyoto, 604-8511, JP
Last Update: 06/12/2025
Shimadzu Corporation has remained committed to commercializing cutting-edge technology and providing it to customers in a wide array of industries for more than 150 years. Our brand statement, "Excellence in Science", reflects our desire and attitude to diligently resp...
ICON plc
ICON plc, South County Business Park, Leopardstown, Dublin, IE, D18 X5R3
Last Update: 02/04/2026
Since our foundation in Dublin, Ireland in 1990, our mission has been to help our clients to accelerate the development of drugs and devices that save lives and improve quality of life. We do this by delivering best in class information, solutions and performance, with ...
Compliance Ranges Comparison
SHIMADZU CORPORATION
ICON plc
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for SHIMADZU CORPORATION in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for ICON plc in 2026.
Incident History - SHIMADZU CORPORATION (X = Date, Y = Severity)
SHIMADZU CORPORATION cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ICON plc (X = Date, Y = Severity)
ICON plc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SHIMADZU CORPORATION
ICON plc
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: *.*.