Comparison Overview
Eczacıbaşı Topluluğu
Eczacıbaşı Topluluğu
Kanyon Ofis Büyükdere Caddesi 185 Levent, Istanbul, 34394, TR
Last Update: 02/04/2026
Dr. Nejat F. Eczacıbaşı tarafından 1942'de temelleri atılan Eczacıbaşı Topluluğu, toplam 41 kuruluşu, 32 üretim tesisi, 13.250’nin üzerinde çalışanı ve 120’nin üzerinde faaliyet gösterdiği uluslararası pazar ile Türkiye'nin önde gelen sanayi toplulukları arasında yer al...
Celestica
5140 Yonge St, Toronto, M2N 6L7, CA
Last Update: 01/04/2026
Celestica is a technology leader dedicated to driving customer success and market advancements. With deep expertise in design, engineering, manufacturing, supply chain and platform solutions, Celestica enables critical data center infrastructure for AI, cloud, and hybri...
Compliance Ranges Comparison
Eczacıbaşı Topluluğu
Celestica
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Eczacıbaşı Topluluğu in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Celestica in 2026.
Incident History - Eczacıbaşı Topluluğu (X = Date, Y = Severity)
Eczacıbaşı Topluluğu cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Celestica (X = Date, Y = Severity)
Celestica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Eczacıbaşı Topluluğu
Celestica
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: *.*.