Comparison Overview
Sampla
Sampla
Via Privata S.P. 215, , ITALY, Caponago (MB), undefined, 20867, IT
Last Update: 14/12/2025
Sampla has been manufacturing lightweight conveyor belts and accessories for over 50 years thanks to our founders’ vision and employees’ fortitude. From PVC and TPU belts produced in Italy, today our strategically located manufacturing facilities can be active also on ...
KUKA
Zugspitzstr. 140, Augsburg, 86165, DE
Last Update: 01/04/2026
KUKA SE & Co. KGaA is a global leader in intelligent automation solutions, generating around 3.7 billion euro in sales and employing approximately 15,000 people worldwide. Headquartered in Augsburg, Germany, KUKA’s mission is to make automation accessible for everyone -...
Compliance Ranges Comparison
Sampla
KUKA
Benchmark & Cyber Underwriting Signals
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Sampla in 2026.
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for KUKA in 2026.
Incident History - Sampla (X = Date, Y = Severity)
Sampla cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KUKA (X = Date, Y = Severity)
KUKA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sampla
KUKA
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: *.*.