Comparison Overview
MassMutual Romania
MassMutual Romania
Șoseaua Orhideelor 15a, București, undefined, 060071, RO
Last Update: 10/12/2025
MassMutual Romania is a technology partner of MassMutual, a leading financial services company in the U.S., with a legacy of more than 170 years. Established in 2020, the Romanian company is building an in-house team passionate about technology and innovation. We have e...
Asurion
1101 Church St, Nashville, 37203, US
Last Update: 23/04/2026
As the world’s leading tech care company, Asurion eliminates the fears and frustrations associated with technology, to ensure our 300 million customers get the most out of their devices, appliances and connections. We provide insurance, repair, replacement, installation...
Compliance Ranges Comparison
MassMutual Romania
Asurion
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for MassMutual Romania in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Asurion has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - MassMutual Romania (X = Date, Y = Severity)
MassMutual Romania cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Asurion (X = Date, Y = Severity)
Asurion cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MassMutual Romania
Asurion
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: *.*.