Comparison Overview
AMMEGA
AMMEGA
Marconistraat 15, Heerhugowaard, North Holland, 1704, NL
Last Update: 01/04/2026
AMMEGA is a global company located in 40 countries. We value our employees, customers, entrepreneurship and we act in an agile and responsible way. Our mission and continuous improvement culture are the foundation for a solid and sustainable business appreciated by our...
Bosch Rexroth
Maria-Theresien-Straße 23, Lohr am Main, 97816, DE
Last Update: 01/04/2026
Bosch Rexroth is a leading provider of automation solutions for industrial and mobile applications. Our innovative products and services enable our customers to move everything that needs to be moved with ease and efficiency, helping them to win in their respective indu...
Compliance Ranges Comparison
AMMEGA
Bosch Rexroth
Benchmark & Cyber Underwriting Signals
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for AMMEGA in 2026.
Incidents vs Automation Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Bosch Rexroth in 2026.
Incident History - AMMEGA (X = Date, Y = Severity)
AMMEGA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bosch Rexroth (X = Date, Y = Severity)
Bosch Rexroth cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AMMEGA
Bosch Rexroth
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: *.*.