Comparison Overview
Moving Magnet Technologies (MMT)
Moving Magnet Technologies (MMT)
1, Rue Christiaan Huygens, Besançon, 25000, FR
Last Update: 01/03/2026
MMT's aim is to provide our customers with the most efficient and reliable contactless solutions for motion control and drive systems. Our team of experts is developing innovative solutions for electromagnetic position sensors, electric motors and actuators. These so...
UGL
Level 8, 40 Miller Street, North Sydney, NSW, AU, 2060
Last Update: 03/04/2026
UGL is CIMIC Group's specialist end-to-end engineering, services and operations provider. We have a rich history dating back to 1899 and since then we have grown to be a market leader in many of the sectors in which we operate. Working with some of the most important c...
Compliance Ranges Comparison
Moving Magnet Technologies (MMT)
UGL
Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Moving Magnet Technologies (MMT) in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for UGL in 2026.
Incident History - Moving Magnet Technologies (MMT) (X = Date, Y = Severity)
Moving Magnet Technologies (MMT) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UGL (X = Date, Y = Severity)
UGL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Moving Magnet Technologies (MMT)
UGL
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: *.*.