Comparison Overview
Bosch Türkiye

Bosch Türkiye
Aydınevler Mahallesi İnönü Caddesi No: 20, İstanbul, 34854, TR
Last Update: 30/03/2026
Türkiye'de ilk kez 1910 yılında kurulan bir temsilcilikle faaliyetlerimize başladık. İlk fabrikamızı 1972 yılında Bursa'da kurduk. Mobilite, Sanayi Teknolojileri, Dayanıklı Tüketim Malları ve Enerji ve Bina Teknolojileri alanlarında beş ayrı şirketle İstanbul, Bursa, Ko...

Parker Hannifin
6035 Parkland Blvd, Cleveland, OH, US, 44124
Last Update: 01/04/2026
Parker Hannifin is a Fortune 250 global leader in motion and control technologies. For more than a century the company has been enabling engineering breakthroughs that lead to a better tomorrow. Learn more at www.parker.com or on Twitter @parkerhannifin. Executive Offi...
Compliance Ranges Comparison

Bosch Türkiye







Parker Hannifin






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Bosch Türkiye in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Parker Hannifin in 2026.
Incident History - Bosch Türkiye (X = Date, Y = Severity)
Bosch Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Parker Hannifin (X = Date, Y = Severity)
Parker Hannifin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bosch Türkiye

Parker Hannifin
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: *.*.