Comparison Overview
Curium Türkiye
Curium Türkiye
Rüzgarlı Bahçe Mahallesi Kavak Sokak No:20, İstanbul, 34805, TR
Last Update: 03/04/2026
Curium is the global leader in nuclear medicine, providing life-changing diagnostics and treatment to patients all over the world. We develop, manufacture and distribute world-class radiopharmaceutical products with a renewed focus on cancer, exploring untapped potenti...
Hikma Pharmaceuticals
1 New Burlington Place, London, W1S 2HR, GB
Last Update: 03/04/2026
For almost 50 years, we’ve been creating high-quality medicines and making them accessible to the people who need them. We are a trusted, reliable partner and dependable source of over 800* high-quality generic, specialty and branded pharmaceutical products that hospita...
Compliance Ranges Comparison
Curium Türkiye
Hikma Pharmaceuticals
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Curium Türkiye in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Hikma Pharmaceuticals in 2026.
Incident History - Curium Türkiye (X = Date, Y = Severity)
Curium Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hikma Pharmaceuticals (X = Date, Y = Severity)
Hikma Pharmaceuticals cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Curium Türkiye
Hikma Pharmaceuticals
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: *.*.